From: Guixin Liu <kanie@linux.alibaba.com>
To: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Nilay Shroff <nilay@linux.ibm.com>,
Daniel Wagner <dwagner@suse.de>, Hannes Reinecke <hare@suse.de>
Cc: linux-nvme@lists.infradead.org
Subject: [PATCH 0/6] nvme: fabrics and target fixes
Date: Fri, 6 Nov 2026 09:58:36 +0800 [thread overview]
Message-ID: <20261106015842.3534898-1-kanie@linux.alibaba.com> (raw)
Six fixes found by code inspection of the nvme host and target drivers:
- a reconnect_delay of 0 is accepted through sysfs and makes the
ctrl_loss_tmo store divide by zero; reproduced on an unfixed
kernel, rejected on the patched one
- list_for_each_entry_safe() in nvme_fc_match_disconn_ls() cannot
tolerate the rport lock drop inside the loop: the cached next
entry may be freed in the window, so the loop switches back to a
plain iterator, which is safe because the reference taken on the
current entry pins it on the list; reproduced under KASAN through
fcloop with an amplified lock-drop window
- a data race on ctrl->transaction between concurrent per-queue
DH-HMAC-CHAP exchanges
- nvmet_subsys_attr_tbkas_store() walks subsys->ctrls without
subsys->lock, the same bug fixed for qid_max_store() in patch 4
of this series
- nvmet_install_queue() leaks a controller reference and permanently
wedges the queue on its error paths
- needless GFP_ATOMIC allocations in the nvmet persistent reservation
code
All fixes are verified on an initiator/target VM pair running the
patched kernel: 30 connect/IO/disconnect cycles, tbkas toggles racing
connection churn, persistent reservation operations across all six
reservation types, and a full DH-HMAC-CHAP authenticated session with
I/O. The nvme-fc fix is additionally exercised through fcloop with
three controllers on one remote port, where the modified
nvme_fc_match_disconn_ls() path ran on every host- and target-initiated
association teardown, including 15 tbkas force-reconnect cycles that
send Disconnect Association LSs into the multi-entry list walk.
Guixin Liu (6):
nvme: reject a reconnect_delay of 0 through sysfs
nvme-fc: fix iterator over rport->ctrl_list in nvme_fc_match_disconn_ls()
nvme-auth: fix data race on ctrl->transaction
nvmet: take subsys->lock in nvmet_subsys_attr_tbkas_store()
nvmet: fix controller reference leak in nvmet_install_queue() error paths
nvmet: use GFP_KERNEL for PR allocations
drivers/nvme/host/auth.c | 2 +-
drivers/nvme/host/fc.c | 4 ++--
drivers/nvme/host/nvme.h | 2 +-
drivers/nvme/host/sysfs.c | 3 +++
drivers/nvme/target/configfs.c | 2 ++
drivers/nvme/target/fabrics-cmd.c | 5 +++++
drivers/nvme/target/pr.c | 4 ++--
7 files changed, 16 insertions(+), 6 deletions(-)
--
2.43.7
next reply other threads:[~2026-11-06 1:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 1:58 Guixin Liu [this message]
2026-11-06 1:58 ` [PATCH 1/6] nvme: reject a reconnect_delay of 0 through sysfs Guixin Liu
2026-11-06 2:09 ` sashiko-bot
2026-11-06 7:39 ` Hannes Reinecke
2026-11-06 10:33 ` Christoph Hellwig
2026-11-06 13:32 ` Nilay Shroff
2026-11-06 1:58 ` [PATCH 2/6] nvme-fc: fix iterator over rport->ctrl_list in nvme_fc_match_disconn_ls() Guixin Liu
2026-11-06 2:06 ` sashiko-bot
2026-11-06 7:38 ` Hannes Reinecke
2026-11-06 10:49 ` Guixin Liu
2026-11-06 1:58 ` [PATCH 3/6] nvme-auth: fix data race on ctrl->transaction Guixin Liu
2026-11-06 7:27 ` Hannes Reinecke
2026-11-06 9:28 ` Guixin Liu
2026-11-06 1:58 ` [PATCH 4/6] nvmet: take subsys->lock in nvmet_subsys_attr_tbkas_store() Guixin Liu
2026-11-06 7:27 ` Hannes Reinecke
2026-11-06 10:34 ` Christoph Hellwig
2026-11-06 13:32 ` Nilay Shroff
2026-11-06 1:58 ` [PATCH 5/6] nvmet: fix controller reference leak in nvmet_install_queue() error paths Guixin Liu
2026-11-06 7:31 ` Hannes Reinecke
2026-11-06 9:29 ` Guixin Liu
2026-11-06 1:58 ` [PATCH 6/6] nvmet: use GFP_KERNEL for PR allocations Guixin Liu
2026-11-06 7:31 ` Hannes Reinecke
2026-11-06 10:35 ` Christoph Hellwig
2026-11-06 13:35 ` Nilay Shroff
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=20261106015842.3534898-1-kanie@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=sagi@grimberg.me \
/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