From: Jason Gunthorpe <jgg@nvidia.com>
To: Jack Wang <jinpu.wang@cloud.ionos.com>
Cc: <linux-rdma@vger.kernel.org>, <bvanassche@acm.org>,
<leon@kernel.org>, <dledford@redhat.com>,
<danil.kipnis@cloud.ionos.com>
Subject: Re: [PATCHv2 for-next 0/4] A few bugfix for RTRS
Date: Fri, 12 Feb 2021 11:40:30 -0400 [thread overview]
Message-ID: <20210212154030.GC1716976@nvidia.com> (raw)
In-Reply-To: <20210212134525.103456-1-jinpu.wang@cloud.ionos.com>
On Fri, Feb 12, 2021 at 02:45:21PM +0100, Jack Wang wrote:
> Hi Jason, hi Doug,
>
> Please consider to include follwing bugfix to next release.
>
> One bugfix for KASAN splat due to we use wrong structure type when send
> RDMA_WRITE_WITH_IMM opcode from me.
>
> One bugfix for allowing addition of random path to exsition session from Haris.
>
> 2 bugfix for memory leak from Gioh.
>
> v2->v1:
> - collect reviewed-by from Leon for patch1 and patch4.
> - adjust patch2 as suggested by Leon, also add missing mutex_unlock before
> return and misc cleanup.
>
> Thanks!
> Jack Wang
>
> Gioh Kim (2):
> RDMA/rtrs-srv: fix memory leak by missing kobject free
> RDMA/rtrs-srv-sysfs: fix missing put_device
>
> Jack Wang (1):
> RDMA/rtrs-srv: Fix BUG: KASAN: stack-out-of-bounds
>
> Md Haris Iqbal (1):
> RDMA/rtrs: Only allow addition of path to an already established
> session
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2021-02-12 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 13:45 [PATCHv2 for-next 0/4] A few bugfix for RTRS Jack Wang
2021-02-12 13:45 ` [PATCHv2 for-next 1/4] RDMA/rtrs-srv: Fix BUG: KASAN: stack-out-of-bounds Jack Wang
2021-02-12 13:45 ` [PATCHv2 for-next 2/4] RDMA/rtrs: Only allow addition of path to an already established session Jack Wang
2021-02-12 13:45 ` [PATCHv2 for-next 3/4] RDMA/rtrs-srv: fix memory leak by missing kobject free Jack Wang
2021-02-12 13:45 ` [PATCHv2 for-next 4/4] RDMA/rtrs-srv-sysfs: fix missing put_device Jack Wang
2021-02-12 15:40 ` Jason Gunthorpe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210212154030.GC1716976@nvidia.com \
--to=jgg@nvidia.com \
--cc=bvanassche@acm.org \
--cc=danil.kipnis@cloud.ionos.com \
--cc=dledford@redhat.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.