From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Bob Pearson <rpearsonhpe@gmail.com>,
dan.carpenter@linaro.org, leon@kernel.org, jgg@nvidia.com,
zyjzyj2000@gmail.com, jhack@hpe.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next] RDMA/rxe: Fix double free in rxe_qp.c
Date: Tue, 16 May 2023 10:10:42 +0800 [thread overview]
Message-ID: <b2d643f7-210f-dad8-ae4b-486b46f20a1e@linux.dev> (raw)
In-Reply-To: <20230515201056.1591140-1-rpearsonhpe@gmail.com>
Hello,
On 5/16/23 04:10, Bob Pearson wrote:
> A recent patch can cause a double spin_unlock_bh() in rxe_qp_to_attr()
> at line 715 in rxe_qp.c. This patch corrects that behavior.
>
> A newer patch from Guoqing Jiang recommends replacing all spin_lock
> calls for qp->state_lock to spin_(un)lock_irqsave(restore)() since
> apparently the blktests test suite can call the kernel verbs APIs
> while in hard interrupt state. This patch needs to be applied first
> and Guoqing's patch modified to accommodate this small change.
If you don't mind, I will send a patch set with your patch as first one,
then
refresh mine. Which means we don't need to keep the second paragraph
in commit message, what do you think?
> Fixes: f605f26ea196 ("RDMA/rxe: Protect QP state with qp->state_lock")
> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> Closes: https://lore.kernel.org/linux-rdma/27773078-40ce-414f-8b97-781954da9f25@kili.mountain/
> Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
> ---
> drivers/infiniband/sw/rxe/rxe_qp.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_qp.c b/drivers/infiniband/sw/rxe/rxe_qp.c
> index c5451a4488ca..245dd36638c7 100644
> --- a/drivers/infiniband/sw/rxe/rxe_qp.c
> +++ b/drivers/infiniband/sw/rxe/rxe_qp.c
> @@ -712,8 +712,9 @@ int rxe_qp_to_attr(struct rxe_qp *qp, struct ib_qp_attr *attr, int mask)
> if (qp->attr.sq_draining) {
> spin_unlock_bh(&qp->state_lock);
> cond_resched();
> + } else {
> + spin_unlock_bh(&qp->state_lock);
> }
> - spin_unlock_bh(&qp->state_lock);
>
> return 0;
> }
Looks good, Acked-by: Guoqing Jiang <guoqing.jiang@linux.dev>
Thanks,
Guoqing
next prev parent reply other threads:[~2023-05-16 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 20:10 [PATCH for-next] RDMA/rxe: Fix double free in rxe_qp.c Bob Pearson
2023-05-16 2:10 ` Guoqing Jiang [this message]
2023-05-16 19:03 ` Bob Pearson
2023-05-17 0:11 ` Jason Gunthorpe
2023-05-17 0:31 ` 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=b2d643f7-210f-dad8-ae4b-486b46f20a1e@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=dan.carpenter@linaro.org \
--cc=jgg@nvidia.com \
--cc=jhack@hpe.com \
--cc=leon@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).