From: Nilay Shroff <nilay@linux.ibm.com>
To: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: hch@lst.de, elver@google.com, kbusch@kernel.org,
sagi@grimberg.me, axboe@fb.com, bvanassche@acm.org,
gjoyce@linux.ibm.com, Nilay Shroff <nilay@linux.ibm.com>
Subject: [PATCH v4 15/20] nvme: add context annotations for nvme_queue::sq_lock
Date: Mon, 13 Jul 2026 17:24:16 +0530 [thread overview]
Message-ID: <20260713115444.465704-16-nilay@linux.ibm.com> (raw)
In-Reply-To: <20260713115444.465704-1-nilay@linux.ibm.com>
nvme_queue::sq_tail, nvme_queue::last_sq_tail and nvme_queue::sq_cmds
are protected by nvme_queue::sq_lock. Annotate each field with
__guarded_by(&sq_lock) and annotate helpers that access them with
__must_hold(&sq_lock) so that Clang's context analysis can validate
the locking requirements.
Access to nvme_queue::sq_tail used solely for tracing is annotated with
data_race(), as they only require a lockless snapshot of the value.
nvme_init_queue() initializes nvme_queue::sq_tail and
nvme_queue::last_sq_tail before the queue is published and thus do not
require nvme_queue::sq_lock protection. So annotate nvme_init_queue()
with context_unsafe() to suppress false positive context analyzer
warning.
nvme_free_queue() operate on queues which are no longer reachable, and
therefore do not require nvme_queue::sq_lock protection. Similarly,
nvme_alloc_sq_cmds() allocates memory for nvme_queue::sq_cmds for the
queue which is not yet published or in use and hence it's safe to
annotate all these helpers using context_unsafe.
Signed-off-by: Nilay Shroff <nilay@linux.ibm.com>
---
drivers/nvme/host/pci.c | 21 +++++++++++++++++----
1 file changed, 17 insertions(+), 4 deletions(-)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 7954417d1252..50ca643c16c5 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -366,7 +366,8 @@ struct nvme_queue {
struct nvme_dev *dev;
struct nvme_descriptor_pools descriptor_pools;
spinlock_t sq_lock;
- void *sq_cmds;
+ void *sq_cmds
+ __guarded_by(&sq_lock);
/* only used for poll queues: */
spinlock_t cq_poll_lock ____cacheline_aligned_in_smp;
struct nvme_completion *cqes;
@@ -375,9 +376,11 @@ struct nvme_queue {
u32 __iomem *q_db;
u32 q_depth;
u16 cq_vector;
- u16 sq_tail;
- u16 last_sq_tail;
u16 cq_head;
+ u16 sq_tail
+ __guarded_by(&sq_lock);
+ u16 last_sq_tail
+ __guarded_by(&sq_lock);
u16 qid;
u8 cq_phase;
u8 sqes;
@@ -716,6 +719,7 @@ static void nvme_pci_map_queues(struct blk_mq_tag_set *set)
* Write sq tail if we are asked to, or if the next command would wrap.
*/
static inline void nvme_write_sq_db(struct nvme_queue *nvmeq, bool write_sq)
+ __must_hold(&nvmeq->sq_lock)
{
if (!write_sq) {
u16 next_tail = nvmeq->sq_tail + 1;
@@ -734,6 +738,7 @@ static inline void nvme_write_sq_db(struct nvme_queue *nvmeq, bool write_sq)
static inline void nvme_sq_copy_cmd(struct nvme_queue *nvmeq,
struct nvme_command *cmd)
+ __must_hold(&nvmeq->sq_lock)
{
memcpy(nvmeq->sq_cmds + (nvmeq->sq_tail << nvmeq->sqes),
absolute_pointer(cmd), sizeof(*cmd));
@@ -1586,7 +1591,12 @@ static inline void nvme_handle_cqe(struct nvme_queue *nvmeq,
return;
}
- trace_nvme_sq(req, cqe->sq_head, nvmeq->sq_tail);
+ /*
+ * Tracing only; annotate a lockless snapshot of nvmeq->sq_tail using
+ * data_race(). This would also help suppress context analysis warning
+ * while accessing nvmeq->sq_tail without acquiring ->sq_lock.
+ */
+ trace_nvme_sq(req, cqe->sq_head, data_race(nvmeq->sq_tail));
if (!nvme_try_complete_req(req, cqe->status, cqe->result) &&
!blk_mq_add_to_batch(req, iob,
nvme_req(req)->status != NVME_SC_SUCCESS,
@@ -2013,6 +2023,7 @@ static enum blk_eh_timer_return nvme_timeout(struct request *req)
}
static void nvme_free_queue(struct nvme_queue *nvmeq)
+ __context_unsafe(/* frees queue which is no longer in use */)
{
dma_free_coherent(nvmeq->dev->dev, CQ_SIZE(nvmeq),
(void *)nvmeq->cqes, nvmeq->cq_dma_addr);
@@ -2107,6 +2118,7 @@ static int nvme_cmb_qdepth(struct nvme_dev *dev, int nr_io_queues,
static int nvme_alloc_sq_cmds(struct nvme_dev *dev, struct nvme_queue *nvmeq,
int qid)
+ __context_unsafe(/* safe to allocate sq_cmds without any protection */)
{
struct pci_dev *pdev = to_pci_dev(dev->dev);
@@ -2181,6 +2193,7 @@ static int queue_request_irq(struct nvme_queue *nvmeq)
}
static void nvme_init_queue(struct nvme_queue *nvmeq, u16 qid)
+ __context_unsafe(/* initialize unpublished/lock-guarded variables */)
{
struct nvme_dev *dev = nvmeq->dev;
--
2.53.0
next prev parent reply other threads:[~2026-07-13 11:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 11:54 [PATCH v4 00/20] Support Clang context analysis for NVMe host drivers Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 01/20] list: introduce LIST_HEAD_GUARDED Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 02/20] list: Permit context-unguarded access with list_empty_careful() Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 03/20] nvme: update nvme_passthru_end() signature Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 04/20] nvme: add context annotations for nvme_passthru_{start|stop} Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 05/20] nvme: add context annotations for nvme_ns_head::srcu Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 06/20] nvme: remove redundant initialization of nvme_ns_head::requeue_list Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 07/20] nvme: add context annotations for nvme_ns_head::requeue_list Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 08/20] nvme: add context annotations for nvme_ns_head::current_path Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 09/20] nvme: add context annotations for nvme_dev::shutdown_lock Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 10/20] nvme: remove redundant initialization of delayed_removal_secs Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 11/20] nvme: add context annotations for nvme_subsystem::lock Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 12/20] nvme: add context annotations for nvme_ctrl::ana_lock Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 13/20] nvme: add context annotations for nvme_subsystems_lock Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 14/20] nvme: add context annotations in fabric.c Nilay Shroff
2026-07-13 11:54 ` Nilay Shroff [this message]
2026-07-13 11:54 ` [PATCH v4 16/20] nvme: add context annotations in rdma.c Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 17/20] nvme: fix context analysis warning " Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 18/20] nvme: add context annotations in tcp.c Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 19/20] nvme: fix context analysis warning " Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 20/20] nvme: enable context analysis support for nvme host driver 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=20260713115444.465704-16-nilay@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=axboe@fb.com \
--cc=bvanassche@acm.org \
--cc=elver@google.com \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--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.