From: Nilay Shroff <nilay@linux.ibm.com>
To: hch@lst.de, kbusch@kernel.org, sagi@grimberg.me, kch@nvidia.com
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
gjoyce@linux.ibm.com, Nilay Shroff <nilay@linux.ibm.com>
Subject: [PATCH v2 0/2] nvmet: fix subtle race in I/O processing and ns configuration
Date: Fri, 18 Sep 2026 21:57:29 +0530 [thread overview]
Message-ID: <20260918162736.802665-1-nilay@linux.ibm.com> (raw)
Hi,
This series addresses two race conditions in the nvmet core code that
handles I/O submission and namespace configuration.
The first patch addresses a race where target namespace attributes
could be changed while I/O is in progress. The second patch addresses
a subtle race that could allow I/O to be admitted even after the
percpu reference count has been killed or marked dead.
As usual, feedback, comments, and suggestions are most welcome!
Thanks!
Changes from v1:
- Replace the XArray mark used to determine whether I/O should be
admitted with an atomic bit. Using an XArray mark would touch
significantly more cache lines in the I/O hot path than a simple
bit test (hch)
- Introduce the NVMET_NS_IO_LIVE namespace flag to address the cache
line overhead of using an XArray mark.
Nilay Shroff (2):
nvmet: defer setting ns->enabled to false in nvmet_ns_disable()
nvmet: don't allow I/O admission after percpu ns reference is killed
drivers/nvme/target/core.c | 28 ++++++++++++++++++----------
drivers/nvme/target/nvmet.h | 2 ++
2 files changed, 20 insertions(+), 10 deletions(-)
--
2.53.0
next reply other threads:[~2026-09-18 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 16:27 Nilay Shroff [this message]
2026-09-18 16:27 ` [PATCH v2 1/2] nvmet: defer setting ns->enabled to false in nvmet_ns_disable() Nilay Shroff
2026-09-21 6:59 ` Christoph Hellwig
2026-10-01 5:55 ` Shin'ichiro Kawasaki
2026-10-01 11:42 ` Nilay Shroff
2026-10-02 3:20 ` Shin'ichiro Kawasaki
2026-09-18 16:27 ` [PATCH v2 2/2] nvmet: don't allow I/O admission after percpu ns reference is killed Nilay Shroff
2026-09-21 6:59 ` Christoph Hellwig
2026-09-22 14:59 ` [PATCH v2 0/2] nvmet: fix subtle race in I/O processing and ns configuration Keith Busch
2026-09-22 15:04 ` Keith Busch
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=20260918162736.802665-1-nilay@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.