Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: zyjzyj2000@gmail.com, jhack@hpe.com, frank.zago@hpe.com,
	linux-rdma@vger.kernel.org
Subject: Re: [PATCH] RDMA/rxe: Fix deadlock in rxe_do_local_ops()
Date: Thu, 30 Jun 2022 20:57:52 -0300	[thread overview]
Message-ID: <20220630235752.GA1083417@nvidia.com> (raw)
In-Reply-To: <20220523223251.15350-1-rpearsonhpe@gmail.com>

On Mon, May 23, 2022 at 05:32:52PM -0500, Bob Pearson wrote:
> When a local operation (invalidate mr, reg mr, bind mw) is finished
> there will be no ack packet coming from a responder to cause the
> wqe to be completed. This may happen anyway if a subsequent wqe
> performs IO. Currently if the wqe is signalled the completer
> tasklet is scheduled immediately but not otherwise.
> 
> This leads to a deadlock if the next wqe has the fence bit set in
> send flags and the operation is not signalled. This patch removes
> the condition that the wqe must be signalled in order to schedule
> the completer tasklet which is the simplest fix for this deadlock
> and is fairly low cost. This is the analog for local operations of
> always setting the ackreq bit in all last or only request packets
> even if the operation is not signalled.
> 
> Reported-by: Jenny Hack <jhack@hpe.com>
> Fixes: c1a411268a4b1 ("RDMA/rxe: Move local ops to subroutine")
> Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
> ---
>  drivers/infiniband/sw/rxe/rxe_req.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)

Applied to for-next, thanks

Jason

  reply	other threads:[~2022-06-30 23:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 22:32 [PATCH for-next] RDMA/rxe: Fix deadlock in rxe_do_local_ops() Bob Pearson
2022-06-30 23:57 ` Jason Gunthorpe [this message]
2022-07-01 15:36   ` [PATCH] " Pearson, Robert B

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=20220630235752.GA1083417@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=frank.zago@hpe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox