[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230111045402.GB15520@lst.de>
Date: Wed, 11 Jan 2023 05:54:02 +0100
From: Christoph Hellwig <hch@....de>
To: Hector Martin <marcan@...can.st>
Cc: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...com>,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
Eric Curtin <ecurtin@...hat.com>, Janne Grunau <j@...nau.net>,
Sven Peter <sven@...npeter.dev>,
Alyssa Rosenzweig <alyssa@...enzweig.io>,
asahi@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] nvme-apple: Do not try to shut down the controller
twice
On Wed, Jan 11, 2023 at 01:36:13PM +0900, Hector Martin wrote:
> The blamed commit stopped explicitly disabling the controller when we do
> a controlled shutdown, but apple_nvme_reset_work was only checking for
> the disable bit before deciding to issue another disable. Check for the
> shutdown state too, to avoid breakage.
>
> This issue does not affect nvme-pci, since it only issues controller
> shutdowns when the system is actually shutting down anyway.
There's a few other places where nvme-pci does a shutdown like
probe/reset failure and most notably and mostly notably various
power management scenarios.
What path is causing a problem here for nvme-apple? I fear we're
missing some highler level check here and getting further out of
sync.
Powered by blists - more mailing lists