All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org, jhack@hpe.com
Subject: Re: [PATCH for-next] RDMA/rxe: Fix ref count error in check_rkey()
Date: Thu, 1 Jun 2023 14:33:25 -0300	[thread overview]
Message-ID: <ZHjWZSWem41svcbM@nvidia.com> (raw)
In-Reply-To: <20230517211509.1819998-1-rpearsonhpe@gmail.com>

On Wed, May 17, 2023 at 04:15:10PM -0500, Bob Pearson wrote:
> There is a reference count error in error path code and a
> potential race in check_rkey() in rxe_resp.c. When looking
> up the rkey for a memory window the reference to the mw from
> rxe_lookup_mw() is dropped before a reference is taken on the
> mr referenced by the mw. If the mr is destroyed immediately
> after the call to rxe_put(mw) the mr pointer is unprotected
> and may end up pointing at freed memory. The rxe_get(mr) call
> should take place before the rxe_put(mw) call.
> 
> All errors in check_rkey() call rxe_put(mw) if mw is not NULL
> but it was already called after the above. The mw pointer
> should be set to NULL after the rxe_put(mw) call to prevent
> this from happening.
> 
> This patch corrects these errors.
> 
> Fixes: cdd0b85675ae ("RDMA/rxe: Implement memory access through MWs")
> Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
> ---
>  drivers/infiniband/sw/rxe/rxe_resp.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

Applied to for-rc, thanks

Jason

  reply	other threads:[~2023-06-01 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 21:15 [PATCH for-next] RDMA/rxe: Fix ref count error in check_rkey() Bob Pearson
2023-06-01 17:33 ` Jason Gunthorpe [this message]
2023-06-01 17:40   ` Bob Pearson

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=ZHjWZSWem41svcbM@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=jhack@hpe.com \
    --cc=linux-rdma@vger.kernel.org \
    --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.