From: Nilay Shroff <nilay@linux.ibm.com>
To: kbusch@kernel.org, hch@lst.de, bvanassche@acm.org,
sagi@grimberg.me, axboe@kernel.dk, chaitanyak@nvidia.com
Cc: gjoyce@linux.ibm.com, elver@google.com,
linux-nvme@lists.infradead.org,
Nilay Shroff <nilay@linux.ibm.com>
Subject: [PATCH v2 00/22] nvmet: add context annotation for params in struct nvmet_ns
Date: Wed, 18 Nov 2026 13:04:41 +0530 [thread overview]
Message-ID: <20261118073505.288910-1-nilay@linux.ibm.com> (raw)
Hi,
This series adds Clang context annotations to fields in struct nvmet_ns
that are protected by nvmet_subsys::lock.
The goal is to incrementally introduce context annotations throughout
the NVMe target code. Covering the entire nvmet subsystem in a single
series would result in a very large patchset with dozens of patches,
making focused review difficult. To keep the changes manageable, I have
split the work into multiple series, each focusing on a specific subset
of context annotations.
This series focuses on fields in struct nvmet_ns protected by
nvmet_subsys::lock. Subsequent series will expand the scope to other
structures and locks.
The patches are organized so that each field is handled incrementally:
first, a field is annotated with __guarded_by(&subsys->lock), and then
any access violations reported by the Clang context analyzer are
addressed in follow-up patches. Not every field annotation necessarily
triggers analyzer warnings. In such cases, the series simply moves on
to the next field.
This approach keeps individual patches focused and makes it easier to
review the annotations and the corresponding locking changes
independently.
As always, review feedback, comments, and suggestions are very welcome!
Changes from v1:
- Dropped patches #6/23 and #7/23, which annotated ns->nsid with
__guarded_by(&ns->subsys->lock). Since ns->nsid is immutable during
the lifetime of a namespace, it does not require additional
protection (Bart Van Assche)
- Since the Clang context analyzer cannot infer that the same lock is
being accessed through different expressions (e.g., subsys->lock and
ns->subsys->lock), pass subsys as an additional argument through the
relevant function call chains and use lockdep_assert_held(&ns->subsys->lock)
instead of __assume_ctx_lock() wherever possible (Bart Van Assche).
Link to v1: https://lore.kernel.org/all/20261109033102.982191-25-nilay@linux.ibm.com/
Nilay Shroff (22):
nvmet: add context annotation for nvmet_ns::bdev
nvmet: fix nvmet_ns::bdev access using nvmet_subsys::lock
nvmet: add context annotation for nvmet_ns::file
nvmet: add context annotation for nvmet_ns::bdev_file
nvmet: add context annotation for nvmet_ns::readonly
nvmet: add context annotation for nvmet_ns::blksize_shift
nvmet: add context annotation for nvmet_ns::size
nvmet: add context annotation for nvmet_ns::nguid
nvmet: add context annotation for nvmet_ns::uuid
nvmet: fix nvmet_ns::uuid access using nvmet_subsys::lock
nvmet: add context annotation for nvmet_ns::buffered_io
nvmet: fix nvmet_ns::buffered_io access using nvmet_subsys::lock
nvmet: add context annotation for nvmet_ns::enabled
nvmet: fix nvmet_ns::enable access using nvmet_subsys::lock
nvmet: add context annotation for nvmet_ns::device_path
nvmet: fix nvmet_ns::device_path access using nvmet_subsys::lock
nvmet: add context annotation for PCI P2P parameters in struct
nvmet_ns
nvmet: fix PCI P2P parameters access using nvmet_subsys::lock
nvmet: add context annotation for integrity params in struct nvmet_ns
nvmet: add context annotation for nvmet_ns::csi
nvmet: fix nvmet_ns::csi access using nvmet_subsys::lock
nvmet: add context annotation for nvmet_ns::debugfs_dir
drivers/nvme/target/admin-cmd.c | 135 ++++++++++-------
drivers/nvme/target/configfs.c | 54 ++++++-
drivers/nvme/target/core.c | 88 +++++++----
drivers/nvme/target/debugfs.h | 6 +-
drivers/nvme/target/io-cmd-bdev.c | 30 ++--
drivers/nvme/target/io-cmd-file.c | 35 +++--
drivers/nvme/target/nvmet.h | 233 +++++++++++++++++++-----------
drivers/nvme/target/rdma.c | 4 +-
drivers/nvme/target/trace.h | 2 +-
drivers/nvme/target/zns.c | 46 +++---
10 files changed, 405 insertions(+), 228 deletions(-)
base-commit: 68099cf27253a8c89d703a282d3d811446d9453b
--
2.53.0
next reply other threads:[~2026-11-18 7:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 7:34 Nilay Shroff [this message]
2026-11-18 7:34 ` [PATCH v2 01/22] nvmet: add context annotation for nvmet_ns::bdev Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 02/22] nvmet: fix nvmet_ns::bdev access using nvmet_subsys::lock Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 03/22] nvmet: add context annotation for nvmet_ns::file Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 04/22] nvmet: add context annotation for nvmet_ns::bdev_file Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 05/22] nvmet: add context annotation for nvmet_ns::readonly Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 06/22] nvmet: add context annotation for nvmet_ns::blksize_shift Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 07/22] nvmet: add context annotation for nvmet_ns::size Nilay Shroff
2026-11-18 7:50 ` sashiko-bot
2026-11-18 7:34 ` [PATCH v2 08/22] nvmet: add context annotation for nvmet_ns::nguid Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 09/22] nvmet: add context annotation for nvmet_ns::uuid Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 10/22] nvmet: fix nvmet_ns::uuid access using nvmet_subsys::lock Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 11/22] nvmet: add context annotation for nvmet_ns::buffered_io Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 12/22] nvmet: fix nvmet_ns::buffered_io access using nvmet_subsys::lock Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 13/22] nvmet: add context annotation for nvmet_ns::enabled Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 14/22] nvmet: fix nvmet_ns::enable access using nvmet_subsys::lock Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 15/22] nvmet: add context annotation for nvmet_ns::device_path Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 16/22] nvmet: fix nvmet_ns::device_path access using nvmet_subsys::lock Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 17/22] nvmet: add context annotation for PCI P2P parameters in struct nvmet_ns Nilay Shroff
2026-11-18 7:34 ` [PATCH v2 18/22] nvmet: fix PCI P2P parameters access using nvmet_subsys::lock Nilay Shroff
2026-11-18 7:55 ` sashiko-bot
2026-11-18 7:35 ` [PATCH v2 19/22] nvmet: add context annotation for integrity params in struct nvmet_ns Nilay Shroff
2026-11-18 7:35 ` [PATCH v2 20/22] nvmet: add context annotation for nvmet_ns::csi Nilay Shroff
2026-11-18 7:35 ` [PATCH v2 21/22] nvmet: fix nvmet_ns::csi access using nvmet_subsys::lock Nilay Shroff
2026-11-18 7:35 ` [PATCH v2 22/22] nvmet: add context annotation for nvmet_ns::debugfs_dir 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=20261118073505.288910-1-nilay@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=chaitanyak@nvidia.com \
--cc=elver@google.com \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox