From: Bart Van Assche <bvanassche@acm.org>
To: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"leon@kernel.org" <leon@kernel.org>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RDMA/srp: Set scmnd->result only when scmnd is not NULL
Date: Tue, 30 Aug 2022 21:04:47 -0700 [thread overview]
Message-ID: <ca74a481-3e80-9a7a-9db7-d766a16d8fd6@acm.org> (raw)
In-Reply-To: <bff7565b-7159-e8f4-e8f5-711994f95056@fujitsu.com>
On 8/30/22 20:16, yangx.jy@fujitsu.com wrote:
> Sorry, I didn't make the right fix. I will send v2 patch.
> I think scmnd may be set to NULL after srp_claim_req() is called and
> then setting scmnd->result can trigger the NULL pointer dereference.
Something like this untested patch may be what you are looking for:
diff --git a/drivers/infiniband/ulp/srp/ib_srp.c
b/drivers/infiniband/ulp/srp/ib_srp.c
index 7720ea270ed8..d7f69e593a63 100644
--- a/drivers/infiniband/ulp/srp/ib_srp.c
+++ b/drivers/infiniband/ulp/srp/ib_srp.c
@@ -1961,7 +1961,8 @@ static void srp_process_rsp(struct srp_rdma_ch
*ch, struct srp_rsp *rsp)
if (scmnd) {
req = scsi_cmd_priv(scmnd);
scmnd = srp_claim_req(ch, req, NULL, scmnd);
- } else {
+ }
+ if (!scmnd) {
shost_printk(KERN_ERR, target->scsi_host,
"Null scmnd for RSP w/tag %#016llx received on ch %td / QP
%#x\n",
rsp->tag, ch - target->ch, ch->qp->qp_num);
Bart.
prev parent reply other threads:[~2022-08-31 4:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 1:47 [PATCH] RDMA/srp: Set scmnd->result only when scmnd is not NULL yangx.jy
2022-08-31 1:59 ` Li Zhijian
2022-08-31 2:31 ` yangx.jy
2022-08-31 3:02 ` Li Zhijian
2022-08-31 2:47 ` Bart Van Assche
2022-08-31 3:16 ` yangx.jy
2022-08-31 4:04 ` Bart Van Assche [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=ca74a481-3e80-9a7a-9db7-d766a16d8fd6@acm.org \
--to=bvanassche@acm.org \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yangx.jy@fujitsu.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