From: Ujwal Kundur <ujwal.kundur@gmail.com>
To: axboe@kernel.dk
Cc: ming.lei@redhat.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ujwal Kundur <ujwal.kundur@gmail.com>,
syzbot+2e9e529ac0b319316453@syzkaller.appspotmail.com
Subject: [PATCH] block: prevent deadlock in del_gendisk()
Date: Sun, 3 Aug 2025 19:11:14 +0530 [thread overview]
Message-ID: <20250803134114.2707-1-ujwal.kundur@gmail.com> (raw)
A potential unsafe locking scenario presents itself when
mutex_lock(&disk->open_mutex) is called with reader's lock held on
update_nr_hwq_lock:
CPU0 CPU1
---- ----
rlock(&set->update_nr_hwq_lock)
lock(&nbd->config_lock);
lock(&set->update_nr_hwq_lock);
lock(&disk->open_mutex)
When the gendisk is added back concurrently, a writer's lock is
attempted to be held on update_nr_hwq_lock while holding other locks in
the call-path, becoming a potential source of deadlock(s).
Scope read-critical section to blk_unregister_queue, which is the only
function that interacts with switching elevator and requires
synchronization with update_nr_hwq_lock.
Reported-by: syzbot+2e9e529ac0b319316453@syzkaller.appspotmail.com
Signed-off-by: Ujwal Kundur <ujwal.kundur@gmail.com>
---
block/genhd.c | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
mode change 100644 => 100755 block/genhd.c
diff --git a/block/genhd.c b/block/genhd.c
old mode 100644
new mode 100755
index c26733f6324b..b56f09f5699b
--- a/block/genhd.c
+++ b/block/genhd.c
@@ -696,6 +696,7 @@ static void __del_gendisk(struct gendisk *disk)
struct block_device *part;
unsigned long idx;
bool start_drain;
+ struct blk_mq_tag_set *set = q->tag_set;
might_sleep();
@@ -740,7 +741,9 @@ static void __del_gendisk(struct gendisk *disk)
bdi_unregister(disk->bdi);
}
+ down_read(&set->update_nr_hwq_lock);
blk_unregister_queue(disk);
+ up_read(&set->update_nr_hwq_lock);
kobject_put(disk->part0->bd_holder_dir);
kobject_put(disk->slave_dir);
@@ -808,20 +811,15 @@ static void disable_elv_switch(struct request_queue *q)
*/
void del_gendisk(struct gendisk *disk)
{
- struct blk_mq_tag_set *set;
unsigned int memflags;
if (!queue_is_mq(disk->queue)) {
__del_gendisk(disk);
} else {
- set = disk->queue->tag_set;
-
disable_elv_switch(disk->queue);
memflags = memalloc_noio_save();
- down_read(&set->update_nr_hwq_lock);
__del_gendisk(disk);
- up_read(&set->update_nr_hwq_lock);
memalloc_noio_restore(memflags);
}
}
--
2.30.2
next reply other threads:[~2025-08-03 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-03 13:41 Ujwal Kundur [this message]
2025-08-04 7:51 ` Yu Kuai
2025-08-05 11:59 ` Hillf Danton
2025-08-06 0:58 ` Yu Kuai
2025-08-06 15:17 ` Ujwal Kundur
2025-08-08 8:41 ` kernel test robot
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=20250803134114.2707-1-ujwal.kundur@gmail.com \
--to=ujwal.kundur@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=syzbot+2e9e529ac0b319316453@syzkaller.appspotmail.com \
/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®