From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org, lizhijian@fujitsu.com
Subject: Re: [PATCH for-next v2] RDMA/rxe: Fix error paths in MR alloc routines
Date: Tue, 2 Aug 2022 14:26:32 -0300 [thread overview]
Message-ID: <YuleSNxp9eb6ZpRa@nvidia.com> (raw)
In-Reply-To: <20220721202213.55061-1-rpearsonhpe@gmail.com>
On Thu, Jul 21, 2022 at 03:22:14PM -0500, Bob Pearson wrote:
> Currently the rxe driver has incorrect code in error paths for
> allocating MR objects. The PD and umem are always freed in
> rxe_mr_cleanup() but in some error paths they are already
> freed or never set. This patch makes sure that the PD is always
> set and checks to see if umem is set before freeing it in
> rxe_mr_cleanup(). umem and map sets are freed if an error
> occurs in an allocate mr call.
>
> Reported-by: Li Zhijian <lizhijian@fujitsu.com>
> Link: https://lore.kernel.org/linux-rdma/11dafa5f-c52d-16c1-fe37-2cd45ab20474@fujitsu.com/
> Fixes: 3902b429ca14 ("Implement invalidate MW operations")
> Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
> ---
> v2:
> Moved setting mr->umem until after checks to avoid sending
> an ERR_PTR to ib_umem_release().
> Cleaned up umem and map sets if errors occur in alloc mr calls.
> Rebased to current for-next.
It seems it doesn't apply now, can you resend on the next rc1?
Thanks,
Jason
prev parent reply other threads:[~2022-08-02 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 20:22 [PATCH for-next v2] RDMA/rxe: Fix error paths in MR alloc routines Bob Pearson
2022-08-02 17:26 ` 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=YuleSNxp9eb6ZpRa@nvidia.com \
--to=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=rpearsonhpe@gmail.com \
--cc=zyjzyj2000@gmail.com \
/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.