possible deadlock in bd_register_pending_holders (3)

Status: upstream: reported on 2025/06/22 16:07
Reported-by: syzbot+99c78ede0917ff97eb31@syzkaller.appspotmail.com
First crash: 446d, last: 9d08h
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in bd_register_pending_holders block 4 3 1773d 1827d 20/29 fixed on 2021/11/10 00:50
upstream possible deadlock in bd_register_pending_holders (2) block 4 4 1736d 1752d 0/29 closed as dup on 2021/11/24 22:11
linux-5.15 possible deadlock in bd_register_pending_holders (2) 4 20 548d 880d 0/3 auto-obsoleted due to no activity on 2025/06/20 22:13
linux-5.15 possible deadlock in bd_register_pending_holders 4 3 1073d 1204d 0/3 auto-obsoleted due to no activity on 2024/01/12 20:03

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.4.895/8310 is trying to acquire lock:
ffff888077bf8118 (&disk->open_mutex){+.+.}-{3:3}, at: bd_register_pending_holders+0x33/0x310 block/holder.c:161

but task is already holding lock:
ffffffff8d197808 (disks_mutex){+.+.}-{3:3}, at: md_alloc+0x48/0xc10 drivers/md/md.c:5723

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #8 (disks_mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       md_alloc+0x48/0xc10 drivers/md/md.c:5723
       add_named_array+0x1bd/0x290 drivers/md/md.c:-1
       param_attr_store+0x20a/0x300 kernel/params.c:585
       module_attr_store+0x5b/0x80 kernel/params.c:905
       kernfs_fop_write_iter+0x3a8/0x500 fs/kernfs/file.c:296
       call_write_iter include/linux/fs.h:2179 [inline]
       new_sync_write fs/read_write.c:507 [inline]
       vfs_write+0x748/0xd70 fs/read_write.c:594
       ksys_write+0x153/0x260 fs/read_write.c:647
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #7 (param_lock){+.+.}-{3:3}:
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       ieee80211_rate_control_ops_get net/mac80211/rate.c:192 [inline]
       rate_control_alloc net/mac80211/rate.c:239 [inline]
       ieee80211_init_rate_ctrl_alg+0x171/0x5e0 net/mac80211/rate.c:983
       ieee80211_register_hw+0x23c6/0x3a60 net/mac80211/main.c:1252
       mac80211_hwsim_new_radio+0x209d/0x4050 drivers/net/wireless/mac80211_hwsim.c:3373
       init_mac80211_hwsim+0x581/0x720 drivers/net/wireless/mac80211_hwsim.c:4607
       do_one_initcall+0x272/0x730 init/main.c:1276
       do_initcall_level+0x13d/0x1f0 init/main.c:1349
       do_initcalls+0x4b/0x90 init/main.c:1365
       kernel_init_freeable+0x3d5/0x560 init/main.c:1589
       kernel_init+0x19/0x1b0 init/main.c:1480
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287

-> #6 (rtnl_mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       rtnl_lock net/core/rtnetlink.c:72 [inline]
       rtnetlink_rcv_msg+0x79f/0xf10 net/core/rtnetlink.c:5695
       netlink_rcv_skb+0x1e9/0x430 net/netlink/af_netlink.c:2519
       netlink_unicast_kernel net/netlink/af_netlink.c:1314 [inline]
       netlink_unicast+0x78f/0x940 net/netlink/af_netlink.c:1340
       netlink_sendmsg+0x8ba/0xbe0 net/netlink/af_netlink.c:1919
       sock_sendmsg_nosec net/socket.c:706 [inline]
       __sock_sendmsg net/socket.c:718 [inline]
       sock_sendmsg net/socket.c:741 [inline]
       kernel_sendmsg+0x23e/0x350 net/socket.c:765
       sock_no_sendpage+0x12a/0x1a0 net/core/sock.c:3044
       kernel_sendpage+0x2cc/0x380 net/socket.c:3549
       sock_sendpage+0x7a/0xb0 net/socket.c:1028
       pipe_to_sendpage+0x22f/0x320 fs/splice.c:364
       splice_from_pipe_feed fs/splice.c:418 [inline]
       __splice_from_pipe+0x333/0x8e0 fs/splice.c:562
       splice_from_pipe fs/splice.c:597 [inline]
       generic_splice_sendpage+0x111/0x180 fs/splice.c:746
       do_splice_from fs/splice.c:767 [inline]
       do_splice+0xe51/0x1620 fs/splice.c:1108
       __do_splice fs/splice.c:1173 [inline]
       __do_sys_splice fs/splice.c:1379 [inline]
       __se_sys_splice+0x34d/0x440 fs/splice.c:1361
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #5 (&pipe->mutex/1){+.+.}-{3:3}:
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       iter_file_splice_write+0x1b6/0xcf0 fs/splice.c:635
       do_splice_from fs/splice.c:767 [inline]
       do_splice+0xe51/0x1620 fs/splice.c:1108
       __do_splice fs/splice.c:1173 [inline]
       __do_sys_splice fs/splice.c:1379 [inline]
       __se_sys_splice+0x34d/0x440 fs/splice.c:1361
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #4 (sb_writers#3){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1817 [inline]
       sb_start_write include/linux/fs.h:1887 [inline]
       file_start_write include/linux/fs.h:3054 [inline]
       lo_write_bvec+0x194/0x780 drivers/block/loop.c:315
       lo_write_simple drivers/block/loop.c:338 [inline]
       do_req_filebacked drivers/block/loop.c:656 [inline]
       loop_handle_cmd drivers/block/loop.c:2235 [inline]
       loop_process_work+0x1b66/0x24c0 drivers/block/loop.c:2275
       process_one_work+0x867/0xff0 kernel/workqueue.c:2310
       worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
       kthread+0x42e/0x520 kernel/kthread.c:334
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287

-> #3 ((work_completion)(&lo->rootcg_work)){+.+.}-{0:0}:
       process_one_work+0x7ba/0xff0 kernel/workqueue.c:2286
       worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
       kthread+0x42e/0x520 kernel/kthread.c:334
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287

-> #2 ((null)){+.+.}-{0:0}:
       flush_workqueue+0x16a/0x1390 kernel/workqueue.c:2830
       drain_workqueue+0xca/0x370 kernel/workqueue.c:2995
       destroy_workqueue+0x7b/0xb20 kernel/workqueue.c:4439
       __loop_clr_fd+0x22f/0xb50 drivers/block/loop.c:1384
       blkdev_put+0x52b/0x780 block/bdev.c:-1
       deactivate_locked_super+0x93/0xf0 fs/super.c:335
       cleanup_mnt+0x426/0x4d0 fs/namespace.c:1148
       task_work_run+0x125/0x1a0 kernel/task_work.c:188
       tracehook_notify_resume include/linux/tracehook.h:189 [inline]
       exit_to_user_mode_loop+0x10f/0x130 kernel/entry/common.c:181
       exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
       __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
       syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
       do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #1 (&lo->lo_mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_killable_nested+0x17/0x20 kernel/locking/mutex.c:758
       lo_open+0x6a/0x100 drivers/block/loop.c:2056
       blkdev_get_whole+0x90/0x390 block/bdev.c:665
       blkdev_get_by_dev+0x2da/0xa50 block/bdev.c:823
       blkdev_open+0x128/0x2c0 block/fops.c:466
       do_dentry_open+0x7f7/0xf90 fs/open.c:826
       do_open fs/namei.c:3659 [inline]
       path_openat+0x2718/0x2fb0 fs/namei.c:3793
       do_filp_open+0x1df/0x400 fs/namei.c:3820
       do_sys_openat2+0x14b/0x500 fs/open.c:1255
       do_sys_open fs/open.c:1271 [inline]
       __do_sys_openat fs/open.c:1287 [inline]
       __se_sys_openat fs/open.c:1282 [inline]
       __x64_sys_openat+0x135/0x160 fs/open.c:1282
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (&disk->open_mutex){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
       lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       bd_register_pending_holders+0x33/0x310 block/holder.c:161
       device_add_disk+0x572/0xd00 block/genhd.c:486
       add_disk include/linux/genhd.h:200 [inline]
       md_alloc+0x80e/0xc10 drivers/md/md.c:5782
       add_named_array+0x1bd/0x290 drivers/md/md.c:-1
       param_attr_store+0x20a/0x300 kernel/params.c:585
       module_attr_store+0x5b/0x80 kernel/params.c:905
       kernfs_fop_write_iter+0x3a8/0x500 fs/kernfs/file.c:296
       call_write_iter include/linux/fs.h:2179 [inline]
       new_sync_write fs/read_write.c:507 [inline]
       vfs_write+0x748/0xd70 fs/read_write.c:594
       ksys_write+0x153/0x260 fs/read_write.c:647
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

Chain exists of:
  &disk->open_mutex --> param_lock --> disks_mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(disks_mutex);
                               lock(param_lock);
                               lock(disks_mutex);
  lock(&disk->open_mutex);

 *** DEADLOCK ***

6 locks held by syz.4.895/8310:
 #0: ffff888076fba5f0 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2bf/0x370 fs/file.c:1056
 #1: ffff88805fa9a460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x296/0xd70 fs/read_write.c:590
 #2: ffff888077bf9c88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1dc/0x500 fs/kernfs/file.c:287
 #3: ffff888144bd8bd0 (kn->active){++++}-{0:0}, at: kernfs_fop_write_iter+0x1fd/0x500 fs/kernfs/file.c:288
 #4: ffffffff8c1d4a08 (param_lock){+.+.}-{3:3}, at: kernel_param_lock kernel/params.c:598 [inline]
 #4: ffffffff8c1d4a08 (param_lock){+.+.}-{3:3}, at: param_attr_store+0xcb/0x300 kernel/params.c:583
 #5: ffffffff8d197808 (disks_mutex){+.+.}-{3:3}, at: md_alloc+0x48/0xc10 drivers/md/md.c:5723

stack backtrace:
CPU: 1 PID: 8310 Comm: syz.4.895 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 bd_register_pending_holders+0x33/0x310 block/holder.c:161
 device_add_disk+0x572/0xd00 block/genhd.c:486
 add_disk include/linux/genhd.h:200 [inline]
 md_alloc+0x80e/0xc10 drivers/md/md.c:5782
 add_named_array+0x1bd/0x290 drivers/md/md.c:-1
 param_attr_store+0x20a/0x300 kernel/params.c:585
 module_attr_store+0x5b/0x80 kernel/params.c:905
 kernfs_fop_write_iter+0x3a8/0x500 fs/kernfs/file.c:296
 call_write_iter include/linux/fs.h:2179 [inline]
 new_sync_write fs/read_write.c:507 [inline]
 vfs_write+0x748/0xd70 fs/read_write.c:594
 ksys_write+0x153/0x260 fs/read_write.c:647
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f395abcb159
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:00007f3958e23028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f395ae52fa0 RCX: 00007f395abcb159
RDX: 0000000000000005 RSI: 0000200000000300 RDI: 0000000000000005
RBP: 00007f395ac62024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f395ae53038 R14: 00007f395ae52fa0 R15: 00007ffe448c0958
 </TASK>

Crashes (25):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/09/02 19:52 linux-5.15.y 0996e0926f6b 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2026/09/01 15:27 linux-5.15.y 28c35638ec51 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2026/08/29 19:22 linux-5.15.y 28c35638ec51 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2026/08/27 18:24 linux-5.15.y 4a1eaf96ee5c 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2026/08/01 04:04 linux-5.15.y 6e2fd6534337 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2026/06/18 15:11 linux-5.15.y dc027a595035 a776b0d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2026/04/07 02:15 linux-5.15.y 91d48252ad4b 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2026/02/06 15:54 linux-5.15.y 9eec9a14ee10 97745f52 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2026/02/03 17:19 linux-5.15.y 9eec9a14ee10 6df4c87a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2026/01/10 05:50 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2026/01/04 22:23 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/12/14 12:20 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/11/27 00:32 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/11/16 15:00 linux-5.15.y cc5ec8769306 f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/11/05 14:15 linux-5.15.y cc5ec8769306 a6c9c731 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/10/26 18:03 linux-5.15.y ac56c046adf4 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/10/13 01:39 linux-5.15.y 29e53a5b1c4f ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/09/09 15:46 linux-5.15.y 7a6c2d093c45 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/09/09 10:24 linux-5.15.y 7a6c2d093c45 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/09/07 18:51 linux-5.15.y 7a6c2d093c45 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/09/03 19:58 linux-5.15.y 01879f56bdde 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/07/30 00:35 linux-5.15.y c79648372d02 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/07/03 21:32 linux-5.15.y 3dea0e7f549e 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/06/30 20:45 linux-5.15.y 3dea0e7f549e 6e83b42d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
2025/06/22 16:06 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in bd_register_pending_holders
* Struck through repros no longer work on HEAD.