====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.3.1331/9475 is trying to acquire lock: ffffffff9133fc80 (disks_mutex){+.+.}-{4:4}, at: md_alloc+0x40/0xf40 drivers/md/md.c:6355 but task is already holding lock: ffffffff9096c160 (major_names_lock){+.+.}-{4:4}, at: blk_probe_dev block/genhd.c:885 [inline] ffffffff9096c160 (major_names_lock){+.+.}-{4:4}, at: blk_request_module+0x35/0x2a0 block/genhd.c:901 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (major_names_lock){+.+.}-{4:4}: __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x197/0x15a0 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:3861 md_add_new_disk+0x522/0x1850 drivers/md/md.c:7681 md_ioctl+0x2027/0x2630 drivers/md/md.c:8525 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 -> #1 (&mddev->reconfig_mutex){+.+.}-{4:4}: __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x197/0x15a0 kernel/locking/mutex.c:821 mddev_lock_nointr drivers/md/md.h:734 [inline] md_alloc+0x81e/0xf40 drivers/md/md.c:6413 md_alloc_and_put+0x1a/0x1f0 drivers/md/md.c:6452 add_named_array+0x240/0x350 drivers/md/md.c:-1 param_attr_store+0x214/0x310 kernel/params.c:591 module_attr_store+0x65/0x90 kernel/params.c:906 kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x612/0xba0 fs/read_write.c:687 ksys_write+0x150/0x270 fs/read_write.c:1036 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 (disks_mutex){+.+.}-{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+0x197/0x15a0 kernel/locking/mutex.c:821 md_alloc+0x40/0xf40 drivers/md/md.c:6355 md_alloc_and_put+0x1a/0x1f0 drivers/md/md.c:6452 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:678 do_dentry_open+0x80e/0x1360 fs/open.c:1000 vfs_open_consume+0x4a/0x350 fs/open.c:1131 do_open fs/namei.c:4851 [inline] path_openat+0x16fc/0x20f0 fs/namei.c:5016 do_file_open+0x23e/0x4a0 fs/namei.c:5045 do_sys_openat2+0x115/0x200 fs/open.c:1442 do_sys_open fs/open.c:1448 [inline] __do_sys_openat fs/open.c:1788 [inline] __se_sys_openat fs/open.c:1783 [inline] __x64_sys_openat+0x138/0x170 fs/open.c:1783 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: disks_mutex --> &mddev->reconfig_mutex --> major_names_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(major_names_lock); lock(&mddev->reconfig_mutex); lock(major_names_lock); lock(disks_mutex); *** DEADLOCK *** locks held by syz.3.1331/9475: 1, last CPU#1: #0: ffffffff9096c160 (major_names_lock){+.+.}-{4:4}, at: blk_probe_dev block/genhd.c:885 [inline] #0: ffffffff9096c160 (major_names_lock){+.+.}-{4:4}, at: blk_request_module+0x35/0x2a0 block/genhd.c:901 stack backtrace: CPU: 1 UID: 0 PID: 9475 Comm: syz.3.1331 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/15/2026 Call Trace: 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+0x197/0x15a0 kernel/locking/mutex.c:821 md_alloc+0x40/0xf40 drivers/md/md.c:6355 md_alloc_and_put+0x1a/0x1f0 drivers/md/md.c:6452 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:678 do_dentry_open+0x80e/0x1360 fs/open.c:1000 vfs_open_consume+0x4a/0x350 fs/open.c:1131 do_open fs/namei.c:4851 [inline] path_openat+0x16fc/0x20f0 fs/namei.c:5016 do_file_open+0x23e/0x4a0 fs/namei.c:5045 do_sys_openat2+0x115/0x200 fs/open.c:1442 do_sys_open fs/open.c:1448 [inline] __do_sys_openat fs/open.c:1788 [inline] __se_sys_openat fs/open.c:1783 [inline] __x64_sys_openat+0x138/0x170 fs/open.c:1783 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:0x7f52f299f559 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:00007f52f38d9028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 00007f52f2c25fa0 RCX: 00007f52f299f559 RDX: 0000000000000002 RSI: 0000200000000180 RDI: ffffffffffffff9c RBP: 00007f52f2a36b50 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f52f2c26038 R14: 00007f52f2c25fa0 R15: 00007ffccc355688 md: async del_gendisk mode will be removed in future, please upgrade to mdadm-4.5+ block device autoloading is deprecated and will be removed.