From: "Maurizio Lombardi" <mlombard@arkamax.eu>
To: "Qing Zhang" <diasyzhangqing@gmail.com>,
<linux-nvme@lists.infradead.org>
Cc: <hch@lst.de>, <sagi@grimberg.me>, <kch@nvidia.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvmet: protect nvmet_ports_list with nvmet_config_sem
Date: Fri, 23 Oct 2026 14:16:30 +0200 [thread overview]
Message-ID: <DMC7LJCQ1QZO.M3C252P8IZG4@arkamax.eu> (raw)
In-Reply-To: <179275538809.275862.8334230595898232727@tencent.com>
On Fri Oct 23, 2026 at 1:36 PM CEST, Qing Zhang wrote:
>>From 554233f4165842a0a104896c30ed4d2e89c11931 Mon Sep 17 00:00:00 2001
> From: Qing Zhang <diasyzhang@tencent.com>
> Date: Fri, 23 Oct 2026 19:29:28 +0800
> Subject: [PATCH] nvmet: protect nvmet_ports_list with nvmet_config_sem
>
> Readers of nvmet_ports_list (e.g. nvmet_subsys_disc_changed()) hold
> nvmet_config_sem and assert it via lockdep. The writers --
> nvmet_ports_make() and nvmet_port_release() -- do not take the lock;
> they rely on the parent directory's VFS inode lock for serialization,
> which is an implementation detail of configfs and not a guaranteed
> contract. Align the writers with the lock the readers already require.
>
> Also move list_add() in nvmet_ports_make() to after the port is fully
> initialized: the old position published the port on the global list
> before INIT_LIST_HEAD(&port->subsystems), so a concurrent reader
> could traverse uninitialized list heads.
>
> flush_workqueue() in nvmet_port_release() stays outside the semaphore
> to avoid a lock dependency on nvmet_wq.
>
> Fixes: b662a078576e ("nvmet: enable Discovery Controller AENs")
> Signed-off-by: Qing Zhang <diasyzhang@tencent.com>
> ---
> drivers/nvme/target/configfs.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/nvme/target/configfs.c b/drivers/nvme/target/configfs.c
> index b03b5d1c2dc3..75cb9e63025f 100644
> --- a/drivers/nvme/target/configfs.c
> +++ b/drivers/nvme/target/configfs.c
> @@ -2009,7 +2009,9 @@ static void nvmet_port_release(struct config_item *item)
>
> /* Let inflight controllers teardown complete */
> flush_workqueue(nvmet_wq);
> + down_write(&nvmet_config_sem);
> list_del(&port->global_entry);
> + up_write(&nvmet_config_sem);
>
> key_put(port->keyring);
> kfree(port);
> @@ -2070,8 +2072,6 @@ static struct config_group *nvmet_ports_make(struct config_group *group,
> port->ana_state[i] = NVME_ANA_INACCESSIBLE;
> }
>
> - list_add(&port->global_entry, &nvmet_ports_list);
> -
> INIT_LIST_HEAD(&port->entry);
> INIT_LIST_HEAD(&port->subsystems);
> INIT_LIST_HEAD(&port->referrals);
> @@ -2105,6 +2105,10 @@ static struct config_group *nvmet_ports_make(struct config_group *group,
> configfs_add_default_group(&port->ana_default_group.group,
> &port->ana_groups_group);
>
> + down_write(&nvmet_config_sem);
> + list_add(&port->global_entry, &nvmet_ports_list);
> + up_write(&nvmet_config_sem);
> +
> return &port->group;
> }
>
Yes, I was already planning to submit the same fix as part of this
larger patch: https://lore.kernel.org/linux-nvme/DLOGQG9GZC3X.1UZ2MY7S3T5N2@arkamax.eu/
but I didn't have time to finish the tests and submit it.
Reviewed-by: Maurizio Lombardi <mlombard@redhat.com>
prev parent reply other threads:[~2026-10-23 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 11:36 Qing Zhang
2026-10-23 12:16 ` Maurizio Lombardi [this message]
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=DMC7LJCQ1QZO.M3C252P8IZG4@arkamax.eu \
--to=mlombard@arkamax.eu \
--cc=diasyzhangqing@gmail.com \
--cc=hch@lst.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®