From: syzbot <syzbot+2e9e529ac0b319316453@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Fix reported __del_gendisk deadlock
Date: Sat, 02 Aug 2025 05:43:20 -0700 [thread overview]
Message-ID: <688e07e8.050a0220.f0410.013c.GAE@google.com> (raw)
In-Reply-To: <6834671a.a70a0220.253bc2.0098.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Fix reported __del_gendisk deadlock
Author: ujwal.kundur@gmail.com
#syz test
diff --git a/block/genhd.c b/block/genhd.c
index c26733f6324b..bad731186189 100644
--- a/block/genhd.c
+++ b/block/genhd.c
@@ -819,9 +819,11 @@ void del_gendisk(struct gendisk *disk)
disable_elv_switch(disk->queue);
memflags = memalloc_noio_save();
+ mutex_lock(&set->tag_list_lock);
down_read(&set->update_nr_hwq_lock);
__del_gendisk(disk);
up_read(&set->update_nr_hwq_lock);
+ mutex_unlock(&set->tag_list_lock);
memalloc_noio_restore(memflags);
}
}
next prev parent reply other threads:[~2025-08-02 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 13:05 [syzbot] [block?] possible deadlock in __del_gendisk syzbot
2025-05-27 3:12 ` syzbot
2025-06-23 4:43 ` Ming Lei
2025-06-23 4:00 ` syzbot
2025-08-02 12:43 ` syzbot [this message]
2025-08-02 12:54 ` Forwarded: Re: Fix reported __del_gendisk deadlock syzbot
2025-08-02 15:25 ` Forwarded: Re: [syzbot] [block?] possible deadlock in __del_gendisk syzbot
2025-08-02 17:55 ` Forwarded: Fix unsafe locking scenario in del_gendisk syzbot
2025-08-02 19:00 ` Forwarded: Re: [syzbot] [block?] possible deadlock in __del_gendisk syzbot
2025-08-02 19:11 ` syzbot
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=688e07e8.050a0220.f0410.013c.GAE@google.com \
--to=syzbot+2e9e529ac0b319316453@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.