[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220215201738.GA26945@lst.de>
Date: Tue, 15 Feb 2022 21:17:38 +0100
From: Christoph Hellwig <hch@....de>
To: Markus Blöchl <markus.bloechl@...tronik.com>
Cc: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
linux-nvme@...ts.infradead.org, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, Stefan Roese <sr@...x.de>
Subject: Re: [RFC PATCH] nvme: prevent hang on surprise removal of NVMe disk
So, I think in th short run setting GD_DEAD is the right thing as a
non-invasive fix, but I'd rather do it in blk_set_queue_dying to also
cover the other drivers with a similar pattern. blk_set_queue_dying
is never used for cases where q->disk isn't valid so that should be
fine.
In the long run I think we just need to remove the fsync_bdev in
del_gendisk or at least make it conditional.
Powered by blists - more mailing lists