From: Christoph Hellwig <hch@lst.de>
To: Eldad.Zinger@dell.com, Leonid.Ravich@emc.com,
Elad.Grupi@dell.com, sagi@grimberg.me,
chaitanya.kulkarni@wdc.com, james.smart@broadcom.com
Cc: linux-nvme@lists.infradead.org
Subject: [PATCH] nvmet-fc: add a missing __rcu annotation to nvmet_fc_tgt_assoc.queues
Date: Sun, 7 Feb 2021 17:20:28 +0100 [thread overview]
Message-ID: <20210207162028.2959778-1-hch@lst.de> (raw)
Make sparse happy after the recent conversion to RCU lookups.
Fixes: 4e2f02bf77da ("nvmet-fc: use RCU proctection for assoc_list")
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
drivers/nvme/target/fc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvme/target/fc.c b/drivers/nvme/target/fc.c
index c14c60bfdf85c6..d375745fc4ed3d 100644
--- a/drivers/nvme/target/fc.c
+++ b/drivers/nvme/target/fc.c
@@ -165,7 +165,7 @@ struct nvmet_fc_tgt_assoc {
struct nvmet_fc_hostport *hostport;
struct nvmet_fc_ls_iod *rcv_disconn;
struct list_head a_list;
- struct nvmet_fc_tgt_queue *queues[NVMET_NR_QUEUES + 1];
+ struct nvmet_fc_tgt_queue __rcu *queues[NVMET_NR_QUEUES + 1];
struct kref ref;
struct work_struct del_work;
struct rcu_head rcu;
--
2.29.2
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-02-07 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 16:20 Christoph Hellwig [this message]
2021-02-07 18:58 ` [PATCH] nvmet-fc: add a missing __rcu annotation to nvmet_fc_tgt_assoc.queues Chaitanya Kulkarni
2021-02-08 23:37 ` James Smart
2021-02-08 23:44 ` Sagi Grimberg
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=20210207162028.2959778-1-hch@lst.de \
--to=hch@lst.de \
--cc=Elad.Grupi@dell.com \
--cc=Eldad.Zinger@dell.com \
--cc=Leonid.Ravich@emc.com \
--cc=chaitanya.kulkarni@wdc.com \
--cc=james.smart@broadcom.com \
--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