From: Avi Weiss <thnkslprpt@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, Avi Weiss <thnkslprpt@gmail.com>,
Josef Bacik <josef@toxicpanda.com>,
Christian Brauner <brauner@kernel.org>,
linux-block@vger.kernel.org
Subject: [PATCH] block: avoid repeated notifications for dead disks
Date: Sat, 31 Oct 2026 19:13:26 +0200 [thread overview]
Message-ID: <20261031171325.4073830-2-thnkslprpt@gmail.com> (raw)
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.
Only report disk death when __blk_mark_disk_dead() first sets GD_DEAD.
Keep its existing return value for queue drain handling in
__del_gendisk().
Fixes: d8530de5a6e8 ("block: call into the file system for bdev_mark_dead")
Signed-off-by: Avi Weiss <thnkslprpt@gmail.com>
---
block/genhd.c | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/block/genhd.c b/block/genhd.c
index 10ca8b4d6eea..a511fc192174 100644
--- a/block/genhd.c
+++ b/block/genhd.c
@@ -657,13 +657,15 @@ static void blk_report_disk_dead(struct gendisk *disk, bool surprise)
rcu_read_unlock();
}
-static bool __blk_mark_disk_dead(struct gendisk *disk)
+static bool __blk_mark_disk_dead(struct gendisk *disk, bool *newly_dead)
{
/*
* Fail any new I/O.
*/
if (test_and_set_bit(GD_DEAD, &disk->state))
return false;
+ if (newly_dead)
+ *newly_dead = true;
if (test_bit(GD_OWNS_QUEUE, &disk->state))
blk_queue_flag_set(QUEUE_FLAG_DYING, disk->queue);
@@ -688,9 +690,12 @@ static bool __blk_mark_disk_dead(struct gendisk *disk)
*/
void blk_mark_disk_dead(struct gendisk *disk)
{
+ bool newly_dead = false;
+
blk_queue_flag_set(QUEUE_FLAG_DYING, disk->queue);
- __blk_mark_disk_dead(disk);
- blk_report_disk_dead(disk, true);
+ __blk_mark_disk_dead(disk, &newly_dead);
+ if (newly_dead)
+ blk_report_disk_dead(disk, true);
}
EXPORT_SYMBOL_GPL(blk_mark_disk_dead);
@@ -727,7 +732,7 @@ 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);
+ start_drain = __blk_mark_disk_dead(disk, NULL);
if (start_drain)
blk_freeze_acquire_lock(q);
xa_for_each_start(&disk->part_tbl, idx, part, 1)
base-commit: 36aad21d50d1af3f6954bb0c988257a908202477
--
2.43.0
reply other threads:[~2026-10-31 17:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261031171325.4073830-2-thnkslprpt@gmail.com \
--to=thnkslprpt@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.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