From: Avi Weiss <thnkslprpt@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Avi Weiss <thnkslprpt@gmail.com>,
Christian Brauner <brauner@kernel.org>,
Josef Bacik <josef@toxicpanda.com>
Subject: [PATCH v2] block: avoid repeated notifications for dead disks
Date: Thu, 5 Nov 2026 10:10:07 +0200 [thread overview]
Message-ID: <20261105081007.816058-2-thnkslprpt@gmail.com> (raw)
In-Reply-To: <20261031171325.4073830-2-thnkslprpt@gmail.com>
blk_mark_disk_dead() reports disk death even when GD_DEAD is already
set. For example, NVMe reset failure and subsequent namespace removal
can call it twice, repeating holder mark_dead callbacks.
Move the GD_DEAD test-and-set into the callers of
__blk_mark_disk_dead() so blk_mark_disk_dead() reports holder death
only on the first transition. Preserve the helper's queue-drain
return value for __del_gendisk().
Fixes: d8530de5a6e8 ("block: call into the file system for bdev_mark_dead")
Signed-off-by: Avi Weiss <thnkslprpt@gmail.com>
---
Updated in v2:
- move the atomic GD_DEAD check into both callers, as suggested by
Christoph Hellwig
- keep the helper signature and queue-drain return semantics unchanged
block/genhd.c | 22 ++++++++++------------
1 file changed, 10 insertions(+), 12 deletions(-)
diff --git a/block/genhd.c b/block/genhd.c
index 10ca8b4d6eea..7e4570f9cea7 100644
--- a/block/genhd.c
+++ b/block/genhd.c
@@ -659,12 +659,6 @@ static void blk_report_disk_dead(struct gendisk *disk, bool surprise)
static bool __blk_mark_disk_dead(struct gendisk *disk)
{
- /*
- * Fail any new I/O.
- */
- if (test_and_set_bit(GD_DEAD, &disk->state))
- return false;
-
if (test_bit(GD_OWNS_QUEUE, &disk->state))
blk_queue_flag_set(QUEUE_FLAG_DYING, disk->queue);
@@ -689,17 +683,19 @@ static bool __blk_mark_disk_dead(struct gendisk *disk)
void blk_mark_disk_dead(struct gendisk *disk)
{
blk_queue_flag_set(QUEUE_FLAG_DYING, disk->queue);
- __blk_mark_disk_dead(disk);
- blk_report_disk_dead(disk, true);
+ if (!test_and_set_bit(GD_DEAD, &disk->state)) {
+ __blk_mark_disk_dead(disk);
+ blk_report_disk_dead(disk, true);
+ }
}
EXPORT_SYMBOL_GPL(blk_mark_disk_dead);
static void __del_gendisk(struct gendisk *disk)
{
struct request_queue *q = disk->queue;
+ bool start_drain = false;
struct block_device *part;
unsigned long idx;
- bool start_drain;
might_sleep();
@@ -727,9 +723,11 @@ static void __del_gendisk(struct gendisk *disk)
* Drop all partitions now that the disk is marked dead.
*/
mutex_lock(&disk->open_mutex);
- start_drain = __blk_mark_disk_dead(disk);
- if (start_drain)
- blk_freeze_acquire_lock(q);
+ if (!test_and_set_bit(GD_DEAD, &disk->state)) {
+ start_drain = __blk_mark_disk_dead(disk);
+ if (start_drain)
+ blk_freeze_acquire_lock(q);
+ }
xa_for_each_start(&disk->part_tbl, idx, part, 1)
drop_partition(part);
mutex_unlock(&disk->open_mutex);
base-commit: 36aad21d50d1af3f6954bb0c988257a908202477
--
2.43.0
prev parent reply other threads:[~2026-11-05 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 17:13 [PATCH] " Avi Weiss
2026-11-03 10:42 ` Christoph Hellwig
2026-11-05 8:10 ` Avi Weiss [this message]
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=20261105081007.816058-2-thnkslprpt@gmail.com \
--to=thnkslprpt@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=hch@infradead.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®