From: Hannes Reinecke <hare@suse.de>
To: Surabhi Gogte <sgogte@purestorage.com>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: Solganik Alexander <sashas@lightbitslabs.com>,
Roy Shterman <roys@lightbitslabs.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
mkhalfella@purestorage.com, randyj@purestorage.com,
adailey@purestorage.com
Subject: Re: [PATCH v3 1/3] nvme-tcp: store and use the caller's network namespace
Date: Mon, 21 Sep 2026 14:32:00 +0200 [thread overview]
Message-ID: <30f9337b-a4b3-4e5c-a6ff-19977d039447@suse.de> (raw)
In-Reply-To: <20260910202812.1642832-2-sgogte@purestorage.com>
On 9/10/26 10:28 PM, Surabhi Gogte wrote:
> nvme_tcp_alloc_queue() creates each socket using
> current->nsproxy->net_ns, which is correct for the initial connect that
> runs in userspace context. However, the reconnect and error recovery
> paths run from a workqueue where current netns is a kernel thread in
> init_net, so sockets created during reconnect end up in a different
> namespace than the one the controller was originally connected from.
>
> Fix this by capturing the caller's network namespace at controller
> allocation time. Use ctrl->net for all socket creation so that every
> queue, on initial connect, reset, or reconnect, is created in the same
> namespace.
>
> Fixes: 3f2304f8c6d6 ("nvme-tcp: add NVMe over TCP host driver")
> Signed-off-by: Surabhi Gogte <sgogte@purestorage.com>
> ---
> drivers/nvme/host/tcp.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
> index 5fda9661bdb7..8e5e22febe2a 100644
> --- a/drivers/nvme/host/tcp.c
> +++ b/drivers/nvme/host/tcp.c
> @@ -171,6 +171,7 @@ struct nvme_tcp_ctrl {
> struct delayed_work connect_work;
> struct nvme_tcp_request async_req;
> u32 io_queues[HCTX_MAX_TYPES];
> + struct net *net;
> };
>
> static struct workqueue_struct *nvme_tcp_wq;
> @@ -1846,7 +1847,7 @@ static int nvme_tcp_alloc_queue(struct nvme_ctrl *nctrl, int qid,
> queue->cmnd_capsule_len = sizeof(struct nvme_command) +
> NVME_TCP_ADMIN_CCSZ;
>
> - ret = sock_create_kern(current->nsproxy->net_ns,
> + ret = sock_create_kern(ctrl->net,
> ctrl->addr.ss_family, SOCK_STREAM,
> IPPROTO_TCP, &queue->sock);
> if (ret) {
> @@ -2638,6 +2639,7 @@ static void nvme_tcp_free_ctrl(struct nvme_ctrl *nctrl)
>
> nvmf_free_options(nctrl->opts);
> free_ctrl:
> + put_net(ctrl->net);
> kfree(ctrl->queues);
> kfree(ctrl);
> }
> @@ -3036,12 +3038,15 @@ static struct nvme_tcp_ctrl *nvme_tcp_alloc_ctrl(struct device *dev,
> goto out_free_ctrl;
> }
>
> + ctrl->net = get_net(current->nsproxy->net_ns);
> +
> ret = nvme_init_ctrl(&ctrl->ctrl, dev, &nvme_tcp_ctrl_ops, 0);
> if (ret)
> goto out_kfree_queues;
>
> return ctrl;
> out_kfree_queues:
> + put_net(ctrl->net);
> kfree(ctrl->queues);
> out_free_ctrl:
> kfree(ctrl);
Reviewed-by: Hannes Reinecke <hare@kernel.org>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2026-09-21 12:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 20:28 [PATCH v3 0/3] nvme-tcp: parallelize I/O setup queue in connect Surabhi Gogte
2026-09-10 20:28 ` [PATCH v3 1/3] nvme-tcp: store and use the caller's network namespace Surabhi Gogte
2026-09-11 21:22 ` Sagi Grimberg
2026-09-21 12:32 ` Hannes Reinecke [this message]
2026-09-10 20:28 ` [PATCH v3 2/3] nvme-tcp: refactor I/O queue setup path Surabhi Gogte
2026-09-11 21:23 ` Sagi Grimberg
2026-09-21 12:34 ` Hannes Reinecke
2026-09-10 20:28 ` [PATCH v3 3/3] nvme-tcp: parallelize I/O queue allocation and startup Surabhi Gogte
2026-09-11 21:27 ` Sagi Grimberg
2026-09-22 19:54 ` Surabhi Gogte (she/her)
2026-09-21 12:37 ` Hannes Reinecke
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=30f9337b-a4b3-4e5c-a6ff-19977d039447@suse.de \
--to=hare@suse.de \
--cc=adailey@purestorage.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mkhalfella@purestorage.com \
--cc=randyj@purestorage.com \
--cc=roys@lightbitslabs.com \
--cc=sagi@grimberg.me \
--cc=sashas@lightbitslabs.com \
--cc=sgogte@purestorage.com \
/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®