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: 123d, last: 4h05m
✨ 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 278d 440d 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 1 11d 11d 0/3 upstream: reported on 2026/09/10 23:54
linux-5.15 possible deadlock in blk_request_module (3) 4 2 149d 171d 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 17d 17d 0/2 upstream: reported on 2026/09/05 07:50
linux-5.15 possible deadlock in blk_request_module 4 6 675d 805d 0/3 auto-obsoleted due to no activity on 2025/02/24 02:18
upstream possible deadlock in blk_request_module block 4 2 1780d 1825d 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.4.200/6538 is trying to acquire lock:
ffffffff8e99c8d8 (major_names_lock){+.+.}-{4:4}, at: blk_probe_dev block/genhd.c:885 [inline]
ffffffff8e99c8d8 (major_names_lock){+.+.}-{4:4}, at: blk_request_module+0x35/0x2a0 block/genhd.c:901

but task is already holding lock:
ffff88802a5c8340 (&mddev->reconfig_mutex){+.+.}-{4:4}, at: mddev_lock drivers/md/md.h:713 [inline]
ffff88802a5c8340 (&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/rtmutex_api.c:561 [inline]
       mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:580
       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/0x470 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/0x470 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+0x1e9/0x630 block/fops.c:665
       do_dentry_open+0x849/0x1420 fs/open.c:996
       vfs_open+0x3b/0x350 fs/open.c:1101
       do_open fs/namei.c:4837 [inline]
       path_openat+0x1448/0x1d60 fs/namei.c:5000
       do_file_open+0x23e/0x4a0 fs/namei.c:5029
       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/rtmutex_api.c:561 [inline]
       mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:580
       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+0x5e6/0x750 block/ioctl.c:798
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:597 [inline]
       __se_sys_ioctl+0xff/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.4.200/6538: 1, last CPU#0:
 #0: ffff88802a5c8340 (&mddev->reconfig_mutex){+.+.}-{4:4}, at: mddev_lock drivers/md/md.h:713 [inline]
 #0: ffff88802a5c8340 (&mddev->reconfig_mutex){+.+.}-{4:4}, at: mddev_suspend_and_lock+0x48/0xf0 drivers/md/md.h:1019

stack backtrace:
CPU: 0 UID: 0 PID: 6538 Comm: syz.4.200 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/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/rtmutex_api.c:561 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:580
 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+0x5e6/0x750 block/ioctl.c:798
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl+0xff/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:0x7fe2689ae159
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:00007fe266be5028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fe268c36090 RCX: 00007fe2689ae159
RDX: 0000200000000400 RSI: 0000000040140921 RDI: 0000000000000003
RBP: 00007fe268a4506b R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fe268c36128 R14: 00007fe268c36090 R15: 00007ffd8664c7e8
 </TASK>
md: could not open device unknown-block(0,0).
md: md_import_device returned -6

Crashes (166):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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/09/22 07:13 upstream f0100363d8c3 e12281bd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/21 11:54 upstream 93f51579e7df 853b104b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/17 11:19 upstream 238650ef6c7c 95928915 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/17 01:40 upstream 9b87fdc9af2f 95928915 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/17 01:30 upstream 9b87fdc9af2f 95928915 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/15 15:05 upstream 587858367581 81a27d1a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_request_module
2026/09/13 16:57 upstream 2f0c1cf72f46 70a60e12 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/13 15:47 upstream 2f0c1cf72f46 70a60e12 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/12 12:31 upstream 5225b8eec4c9 70a60e12 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_request_module
2026/09/06 18:24 upstream 1fc5a74b108f 4f7b22a0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/06 02:35 upstream 214f4aeb2255 4f7b22a0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/04 05:19 upstream 841e384b841a 801f0966 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_request_module
2026/09/21 13:11 upstream 93f51579e7df 853b104b .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/21 09:39 upstream 93f51579e7df 853b104b .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/21 07:42 upstream 93f51579e7df 853b104b .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/21 03:20 upstream 518e5b794c06 853b104b .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/20 23:39 upstream 518e5b794c06 853b104b .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/20 22:12 upstream 518e5b794c06 853b104b .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/19 05:23 upstream 40288c9206c1 853b104b .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/17 07:10 upstream 238650ef6c7c 95928915 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/16 09:25 upstream f6e7b42bf05b 12a0a44a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/16 08:18 upstream f6e7b42bf05b 12a0a44a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/15 07:33 upstream 587858367581 81a27d1a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/15 01:23 upstream 587858367581 81a27d1a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/14 22:26 upstream 704340f1cd0d 924033e8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/14 16:14 upstream 704340f1cd0d 924033e8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/14 10:04 upstream 704340f1cd0d 70a60e12 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/13 00:54 upstream 5225b8eec4c9 70a60e12 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/12 09:35 upstream 827751b699b7 70a60e12 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/12 02:23 upstream 827751b699b7 70a60e12 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/11 12:36 upstream 08df884136f1 9c29f801 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/11 10:03 upstream 50d05c7c76c9 1fe56c0a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/11 07:27 upstream 50d05c7c76c9 1fe56c0a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/11 06:06 upstream 50d05c7c76c9 1fe56c0a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/10 12:23 upstream 50d05c7c76c9 1fe56c0a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/09 14:34 upstream 893e11787f78 edec9137 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/08 20:16 upstream 5acbae5f7eb3 351387c4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/07 21:07 upstream df2908090cda 5e4626f5 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/07 01:31 upstream 1fc5a74b108f 4f7b22a0 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/05 10:45 upstream 654ae5d73c05 4f7b22a0 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/05 00:53 upstream 654ae5d73c05 4f7b22a0 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/04 00:23 upstream 8ab1afb2eb24 801f0966 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/03 09:07 upstream 940de590b839 6a988719 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_request_module
2026/09/15 22:04 linux-next 9d80aa4617b3 81a27d1a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_request_module
2026/09/12 13:41 linux-next a9d7ced84989 70a60e12 .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/10 03:51 linux-next a9d7ced84989 4e8b1cc6 .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/04 07:38 linux-next 9d80aa4617b3 801f0966 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root 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.