possible deadlock in blk_request_module (2)

Status: upstream: reported on 2026/05/25 20:24
Subsystems: raid
Labels: prio:low
[Documentation on labels]
Reported-by: syzbot+fb0ff9bfe34ad282ebd4@syzkaller.appspotmail.com
First crash: 146d, last: 5h14m
▶ ▼ ✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision
5aabafd3 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ possible deadlock in blk_request_module (2) 2026/06/02 05:12 2026/06/02 05:12 2026/06/02 05:18 1095583b
▶ ▼ Discussions (3)
Title Replies (including bot) Last reply
Re: [PATCH v3] loop: Fix NULL pointer dereference in lo_rw_aio() 8 (8) 2026/05/30 23:57
[PATCH] block: assign caller-specific lockdep class to disk->open_mutex 2 (2) 2026/05/30 22:50
[syzbot] [block?] possible deadlock in blk_request_module (2) 0 (1) 2026/05/25 20:24
▶ ▼ Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in blk_request_module (2) 4 6 301d 463d 0/3 auto-obsoleted due to no activity on 2026/03/27 18:48
linux-5.15 possible deadlock in blk_request_module (4) 4 5 4d14h 34d 0/3 upstream: reported on 2026/09/10 23:54
linux-5.15 possible deadlock in blk_request_module (3) 4 2 171d 194d 0/3 auto-obsoleted due to no activity on 2026/08/04 13:53
linux-6.6 possible deadlock in blk_request_module 4 1 40d 40d 0/2 upstream: reported on 2026/09/05 07:50
linux-5.15 possible deadlock in blk_request_module 4 6 698d 828d 0/3 auto-obsoleted due to no activity on 2025/02/24 02:18
upstream possible deadlock in blk_request_module block 4 2 1803d 1848d 0/29 auto-closed as invalid on 2022/03/06 21:21

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.503/8333 is trying to acquire lock:
ffffffff90554720 (major_names_lock){+.+.}-{4:4}, at: blk_probe_dev block/genhd.c:885 [inline]
ffffffff90554720 (major_names_lock){+.+.}-{4:4}, at: blk_request_module+0x35/0x2a0 block/genhd.c:901

but task is already holding lock:
ffff888037bc2358 (&mddev->reconfig_mutex){+.+.}-{4:4}, at: mddev_lock drivers/md/md.h:713 [inline]
ffff888037bc2358 (&mddev->reconfig_mutex){+.+.}-{4:4}, at: mddev_suspend_and_lock+0x48/0xf0 drivers/md/md.h:1019

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&mddev->reconfig_mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821
       mddev_lock_nointr drivers/md/md.h:734 [inline]
       md_start_sync+0x179/0x1010 drivers/md/md.c:10275
       process_one_work kernel/workqueue.c:3396 [inline]
       process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3479
       worker_thread+0xa47/0xfb0 kernel/workqueue.c:3560
       kthread+0x38b/0x480 kernel/kthread.c:436
       ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #2 ((work_completion)(&mddev->sync_work)){+.+.}-{0:0}:
       process_one_work kernel/workqueue.c:3372 [inline]
       process_scheduled_works+0xc03/0x1630 kernel/workqueue.c:3479
       worker_thread+0xa47/0xfb0 kernel/workqueue.c:3560
       kthread+0x38b/0x480 kernel/kthread.c:436
       ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #1 ((wq_completion)md_misc){+.+.}-{0:0}:
       touch_wq_lockdep_map+0xcb/0x180 kernel/workqueue.c:4111
       __flush_workqueue+0x148/0x1470 kernel/workqueue.c:4153
       md_alloc+0x32/0xf20 drivers/md/md.c:6334
       md_alloc_and_put+0x1a/0x1f0 drivers/md/md.c:6423
       blk_probe_dev block/genhd.c:888 [inline]
       blk_request_module+0x27d/0x2a0 block/genhd.c:-1
       blkdev_get_no_open+0x3f/0xe0 block/bdev.c:870
       blkdev_open+0x1d7/0x600 block/fops.c:670
       do_dentry_open+0x816/0x1380 fs/open.c:996
       vfs_open+0x3b/0x340 fs/open.c:1101
       do_open fs/namei.c:4866 [inline]
       path_openat+0x1443/0x1d60 fs/namei.c:5029
       do_file_open+0x23e/0x4a0 fs/namei.c:5058
       do_sys_openat2+0x115/0x200 fs/open.c:1417
       do_sys_open fs/open.c:1423 [inline]
       __do_sys_openat fs/open.c:1439 [inline]
       __se_sys_openat fs/open.c:1434 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1434
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (major_names_lock){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3209 [inline]
       check_prevs_add kernel/locking/lockdep.c:3328 [inline]
       validate_chain kernel/locking/lockdep.c:3952 [inline]
       __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288
       lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821
       blk_probe_dev block/genhd.c:885 [inline]
       blk_request_module+0x35/0x2a0 block/genhd.c:901
       blkdev_get_no_open+0x3f/0xe0 block/bdev.c:870
       bdev_file_open_by_dev+0xa0/0x240 block/bdev.c:1091
       md_import_device+0x2e9/0x650 drivers/md/md.c:3847
       md_add_new_disk+0x669/0x1850 drivers/md/md.c:7549
       md_ioctl+0x200a/0x2610 drivers/md/md.c:8499
       blkdev_ioctl+0x5e3/0x740 block/ioctl.c:798
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:597 [inline]
       __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  major_names_lock --> (work_completion)(&mddev->sync_work) --> &mddev->reconfig_mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&mddev->reconfig_mutex);
                               lock((work_completion)(&mddev->sync_work));
                               lock(&mddev->reconfig_mutex);
  lock(major_names_lock);

 *** DEADLOCK ***

locks held by syz.0.503/8333: 1, last CPU#0:
 #0: ffff888037bc2358 (&mddev->reconfig_mutex){+.+.}-{4:4}, at: mddev_lock drivers/md/md.h:713 [inline]
 #0: ffff888037bc2358 (&mddev->reconfig_mutex){+.+.}-{4:4}, at: mddev_suspend_and_lock+0x48/0xf0 drivers/md/md.h:1019

stack backtrace:
CPU: 0 UID: 0 PID: 8333 Comm: syz.0.503 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/05/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2087
 check_noncircular+0x12f/0x150 kernel/locking/lockdep.c:2219
 check_prev_add kernel/locking/lockdep.c:3209 [inline]
 check_prevs_add kernel/locking/lockdep.c:3328 [inline]
 validate_chain kernel/locking/lockdep.c:3952 [inline]
 __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288
 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
 __mutex_lock_common kernel/locking/mutex.c:646 [inline]
 __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821
 blk_probe_dev block/genhd.c:885 [inline]
 blk_request_module+0x35/0x2a0 block/genhd.c:901
 blkdev_get_no_open+0x3f/0xe0 block/bdev.c:870
 bdev_file_open_by_dev+0xa0/0x240 block/bdev.c:1091
 md_import_device+0x2e9/0x650 drivers/md/md.c:3847
 md_add_new_disk+0x669/0x1850 drivers/md/md.c:7549
 md_ioctl+0x200a/0x2610 drivers/md/md.c:8499
 blkdev_ioctl+0x5e3/0x740 block/ioctl.c:798
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fec4319e2d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fec43f7f028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fec43426090 RCX: 00007fec4319e2d9
RDX: 0000200000000420 RSI: 0000000040140921 RDI: 0000000000000005
RBP: 00007fec43235888 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fec43426128 R14: 00007fec43426090 R15: 00007fff4a1987a8
 </TASK>
md: could not open device unknown-block(0,0).
md: md_import_device returned -6

Crashes (260):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/10/13 15:08 upstream 24a19b953e2a 7321cd29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/10/12 20:40 upstream 24a19b953e2a 745a967f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_request_module
2026/10/09 18:39 upstream af32da41b032 a8add9cd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/10/08 01:18 upstream 602042bf29f6 6520ecdb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/10/07 23:20 upstream 602042bf29f6 6520ecdb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/10/06 08:27 upstream 2c3418fffa9d f7710056 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/10/04 23:09 upstream 6addb4f38557 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/30 00:42 upstream 6f8319e3e9a4 7808aef4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/30 00:02 upstream 6f8319e3e9a4 7808aef4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/27 22:09 upstream 104484baf748 a3c7249d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/27 08:45 upstream fd179f8a05be a3c7249d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/26 18:24 upstream 6812ce4e4379 a3c7249d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/22 10:27 upstream f0100363d8c3 e12281bd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_request_module
2026/10/15 06:06 upstream 0fcb05b72344 8fb0ae89 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/15 01:02 upstream 0fcb05b72344 8fb0ae89 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/14 14:13 upstream 4056b3c9d3c9 1a71827b .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/14 03:09 upstream ca3e345926b0 7321cd29 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/12 21:56 upstream 24a19b953e2a 745a967f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/12 09:31 upstream b88c841d1164 4f92358f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/09 21:15 upstream af32da41b032 549ef7e3 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/09 16:06 upstream af32da41b032 549ef7e3 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/05 17:16 upstream 67f0943b394d af63e995 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/05 07:12 upstream a90ee4305c4a 57bbd979 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/03 11:01 upstream e767a4ea70a3 57bbd979 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/03 06:34 upstream 5e0f8396d480 57bbd979 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/03 04:13 upstream 5e0f8396d480 57bbd979 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/02 21:30 upstream 5e0f8396d480 57bbd979 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/02 17:57 upstream ce1e0223d8ad 1065c8fa .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/01 23:55 upstream d24e8ac715de 6d32eb1f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/01 20:49 upstream d24e8ac715de 6d32eb1f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/01 02:06 upstream 551c722f4080 4db88980 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/01 01:00 upstream 551c722f4080 4db88980 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/30 18:35 upstream 551c722f4080 4db88980 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/29 06:51 upstream 72d3fcf802c4 7bf4ea23 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/29 03:45 upstream 72d3fcf802c4 a7db5c9f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/28 18:32 upstream 72d3fcf802c4 a7db5c9f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/28 12:29 upstream 72d3fcf802c4 a3c7249d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/28 11:06 upstream 72d3fcf802c4 a3c7249d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/28 02:12 upstream d266640c6c76 a3c7249d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/27 20:06 upstream d266640c6c76 a3c7249d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/27 15:17 upstream fd179f8a05be a3c7249d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/26 21:09 upstream 6812ce4e4379 a3c7249d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/26 10:27 upstream f14572c203d5 a3c7249d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/26 00:28 upstream f14572c203d5 f281d9d2 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/25 10:40 upstream 165768bb7026 f281d9d2 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/10/13 10:10 linux-next 4eb2586bd40d 745a967f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in blk_request_module
2026/10/10 15:04 linux-next becb95e45ef0 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/10/10 10:40 linux-next becb95e45ef0 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in blk_request_module
2026/10/10 07:03 linux-next becb95e45ef0 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/10/09 13:00 linux-next aac26bee2287 a8add9cd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/10/08 23:56 linux-next b01868671970 b2734a59 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/10/08 12:51 linux-next b01868671970 4f6a9fcf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/10/07 20:16 linux-next b01868671970 6520ecdb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/10/07 18:32 linux-next b01868671970 6520ecdb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/10/07 17:25 linux-next b01868671970 6520ecdb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/10/05 20:31 linux-next bf1ee2bd5c2d 1995e6c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/10/01 15:24 linux-next 6c2cb8b8b843 38f7f0d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in blk_request_module
2026/09/27 10:02 linux-next f5f84daefcd9 a3c7249d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/09/26 22:53 linux-next f5f84daefcd9 a3c7249d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/09/25 12:12 linux-next 4c253ac4b29b f281d9d2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/05/26 05:42 linux-next c1ecb239fa34 c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/05/25 09:22 linux-next c1ecb239fa34 c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/05/21 20:20 linux-next 550604d6c9b9 e195359d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
* Struck through repros no longer work on HEAD.