From: Hannes Reinecke <hare@suse.de>
To: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>,
Justin Tee <justin.tee@broadcom.com>,
Naresh Gottumukkala <nareshgottumukkala83@gmail.com>,
Paul Ely <paul.ely@broadcom.com>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>
Cc: Daniel Wagner <wagi@kernel.org>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
syzbot+77955102efac681ec73b@syzkaller.appspotmail.com
Subject: Re: [PATCH] nvmet-fcloop: fail LS request synchronously when remote port is gone
Date: Mon, 21 Sep 2026 11:00:38 +0200 [thread overview]
Message-ID: <0d816796-3641-4982-9b28-484b226021f5@suse.de> (raw)
In-Reply-To: <20260920163804.67858-1-ngocthang2710.1999@gmail.com>
On 9/20/26 6:38 PM, Nguyen Ngoc Thang wrote:
> fcloop_t2h_ls_req() handles a missing remoteport by queueing the request
> on tport->ls_list and completing it with -ECONNREFUSED from a work item.
>
> nvmet_fc_delete_assoc_work() sends the Disconnect Association LS this
> way. When it runs during nvmet_fc_unregister_targetport(), the work is
> queued after flush_workqueue() has started, so it is not waited for.
> nvmet_fc_free_pending_reqs() then frees the still-pending lsop and the
> late work item calls lsreq->done() on freed memory:
>
> BUG: KASAN: slab-use-after-free in fcloop_rport_lsrqst_work+0x242/0x2e0
> Workqueue: nvmet-wq fcloop_tport_lsrqst_work
> Allocated by nvmet_fc_xmt_disconnect_assoc
> Freed by nvmet_fc_free_pending_reqs
> nvmet_fc_unregister_targetport
> fcloop_delete_target_port
>
> Return -ECONNREFUSED directly instead. __nvmet_fc_send_ls_req() unwinds
> and nvmet_fc_xmt_disconnect_assoc() frees the lsop, so no completion is
> left outstanding.
>
> Reported-by: syzbot+77955102efac681ec73b@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=77955102efac681ec73b
> Fixes: bbccbf791e6f ("nvmet-fc: free pending reqs on tgtport unregister")
> Signed-off-by: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>
> ---
> drivers/nvme/target/fcloop.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/nvme/target/fcloop.c b/drivers/nvme/target/fcloop.c
> index b63af3b643a6..9f9fb40f8a97 100644
> --- a/drivers/nvme/target/fcloop.c
> +++ b/drivers/nvme/target/fcloop.c
> @@ -456,21 +456,18 @@ fcloop_t2h_ls_req(struct nvmet_fc_target_port *targetport, void *hosthandle,
> * 1:1 tgtport vs remoteport
> */
>
> + /*
> + * Fail synchronously: an async completion can run after
> + * nvmet_fc_unregister_targetport() has freed the pending lsreq.
> + */
> + if (!tport->remoteport)
> + return -ECONNREFUSED;
> +
> tls_req = kmem_cache_alloc(lsreq_cache, GFP_KERNEL);
> if (!tls_req)
> return -ENOMEM;
> tls_req->lsreq = lsreq;
> INIT_LIST_HEAD(&tls_req->ls_list);
> -
> - if (!tport->remoteport) {
> - tls_req->status = -ECONNREFUSED;
> - spin_lock(&tport->lock);
> - list_add_tail(&tls_req->ls_list, &tport->ls_list);
> - spin_unlock(&tport->lock);
> - queue_work(nvmet_wq, &tport->ls_work);
> - return ret;
> - }
> -
> tls_req->status = 0;
> ret = nvme_fc_rcv_ls_req(tport->remoteport, &tls_req->ls_rsp,
> lsreq->rqstaddr, lsreq->rqstlen);
Can you create a blktest for this?
Otherwise look good.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2026-09-21 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 16:38 Nguyen Ngoc Thang
2026-09-21 9:00 ` Hannes Reinecke [this message]
2026-09-21 11:28 ` Daniel Wagner
2026-09-21 14:59 ` Nguyen Ngoc Thang
2026-09-21 14:56 ` [PATCH v2] nvmet-fc: flush nvmet_wq twice on targetport unregister Nguyen Ngoc Thang
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=0d816796-3641-4982-9b28-484b226021f5@suse.de \
--to=hare@suse.de \
--cc=hch@lst.de \
--cc=justin.tee@broadcom.com \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nareshgottumukkala83@gmail.com \
--cc=ngocthang2710.1999@gmail.com \
--cc=paul.ely@broadcom.com \
--cc=sagi@grimberg.me \
--cc=syzbot+77955102efac681ec73b@syzkaller.appspotmail.com \
--cc=wagi@kernel.org \
/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
all inboxes | Powered by JetHome®