From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next] RDMA/rxe: Fix qp reference counting for atomic ops
Date: Wed, 16 Jun 2021 20:21:20 -0300 [thread overview]
Message-ID: <20210616232120.GA1888697@nvidia.com> (raw)
In-Reply-To: <20210604230558.4812-1-rpearsonhpe@gmail.com>
On Fri, Jun 04, 2021 at 06:05:59PM -0500, Bob Pearson wrote:
> Currently the rdma_rxe driver attempts to protect atomic responder
> resources by taking a reference to the qp which is only freed when the
> resource is recycled for a new read or atomic operation. This means that
> in normal circumstances there is almost always an extra qp reference
> once an atomic operation has been executed which prevents cleaning up
> the qp and associated pd and cqs when the qp is destroyed.
>
> This patch removes the call to rxe_add_ref() in send_atomic_ack() and the
> call to rxe_drop_ref() in free_rd_atomic_resource(). If the qp is
> destroyed while a peer is retrying an atomic op it will cause the
> operation to fail which is acceptable.
>
> Reported-by: Zhu Yanjun <zyjzyj2000@gmail.com>
> Fixes: 86af61764151 ("IB/rxe: remove unnecessary skb_clone")
> Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
> ---
> drivers/infiniband/sw/rxe/rxe_qp.c | 1 -
> drivers/infiniband/sw/rxe/rxe_resp.c | 2 --
> 2 files changed, 3 deletions(-)
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2021-06-16 23:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 23:05 [PATCH for-next] RDMA/rxe: Fix qp reference counting for atomic ops Bob Pearson
2021-06-04 23:18 ` Bob Pearson
2021-06-07 8:16 ` Zhu Yanjun
2021-06-07 11:03 ` Leon Romanovsky
2021-06-07 11:12 ` Zhu Yanjun
2021-06-07 16:14 ` Pearson, Robert B
2021-06-08 1:39 ` Zhu Yanjun
2021-06-08 2:01 ` Pearson, Robert B
2021-06-08 3:48 ` Zhu Yanjun
2021-06-08 4:49 ` Pearson, Robert B
2021-06-07 16:11 ` Pearson, Robert B
2021-06-16 23:21 ` 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=20210616232120.GA1888697@nvidia.com \
--to=jgg@nvidia.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