[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175456970208.305227.5090103339122864119.b4-ty@kernel.dk>
Date: Thu, 07 Aug 2025 06:28:22 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Yi Zhang <yi.zhang@...hat.com>, Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>, Chaitanya Kulkarni <kch@...dia.com>,
Keith Busch <kbusch@...nel.org>,
Mohamed Khalfella <mkhalfella@...estorage.com>
Cc: Shinichiro Kawasaki <shinichiro.kawasaki@....com>,
Hannes Reinecke <hare@...nel.org>, Daniel Wagner <dwagner@...e.de>,
Maurizio Lombardi <mlombard@...hat.com>,
Randy Jennings <randyj@...estorage.com>, linux-nvme@...ts.infradead.org,
linux-block <linux-block@...r.kernel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nvmet: exit debugfs after discovery subsystem exits
On Wed, 06 Aug 2025 22:35:07 -0700, Mohamed Khalfella wrote:
> Commit 528589947c180 ("nvmet: initialize discovery subsys after debugfs
> is initialized") changed nvmet_init() to initialize nvme discovery after
> "nvmet" debugfs directory is initialized. The change broke nvmet_exit()
> because discovery subsystem now depends on debugfs. Debugfs should be
> destroyed after discovery subsystem. Fix nvmet_exit() to do that.
>
>
> [...]
Applied, thanks!
[1/1] nvmet: exit debugfs after discovery subsystem exits
commit: 80f21806b8e34ae1e24c0fc6a0f0dfd9b055e130
Best regards,
--
Jens Axboe
Powered by blists - more mailing lists