[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250729102505.lxot5ka473gh4uyh@green245.gost>
Date: Tue, 29 Jul 2025 15:55:05 +0530
From: Nitesh Shetty <nj.shetty@...sung.com>
To: Mohamed Khalfella <mkhalfella@...estorage.com>
Cc: Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>,
Chaitanya Kulkarni <kch@...dia.com>, Keith Busch <kbusch@...nel.org>, Hannes
Reinecke <hare@...nel.org>, Daniel Wagner <dwagner@...e.de>, Randy Jennings
<randyj@...estorage.com>, linux-nvme@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nvmet: Initialize discovery subsys after debugfs is
initialized
On 25/07/25 01:50PM, Mohamed Khalfella wrote:
>During nvme target initialization discovery subsystem is initialized
>before "nvmet" debugfs directory is created. This results in discovery
>subsystem debugfs directory to be created in debugfs root directory.
>
>nvmet_init() ->
> nvmet_init_discovery() ->
> nvmet_subsys_alloc() ->
> nvmet_debugfs_subsys_setup()
>
>In other words, the codepath above is exeucted before nvmet_debugfs is
>created. We get /sys/kernel/debug/nqn.2014-08.org.nvmexpress.discovery
>instead of /sys/kernel/debug/nvmet/nqn.2014-08.org.nvmexpress.discovery.
>Move nvmet_init_discovery() call after nvmet_init_debugfs() to fix it.
>
>Fixes: 649fd41420a8 ("nvmet: add debugfs support")
>Signed-off-by: Mohamed Khalfella <mkhalfella@...estorage.com>
>---
Reviewed-by: Nitesh Shetty <nj.shetty@...sung.com>
Powered by blists - more mailing lists