REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected 5.15.179-syzkaller #0 Not tainted ------------------------------------------------------ syz.0.334/5206 is trying to acquire lock: ffff88802c295090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27 but task is already holding lock: ffff888067f182e0 (&type->i_mutex_dir_key#19/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline] ffff888067f182e0 (&type->i_mutex_dir_key#19/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3835 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&type->i_mutex_dir_key#19/1){+.+.}-{3:3}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 down_write_nested+0x3b/0x60 kernel/locking/rwsem.c:1667 inode_lock_nested include/linux/fs.h:822 [inline] filename_create+0x25c/0x530 fs/namei.c:3835 do_mknodat+0x176/0x690 fs/namei.c:3981 __do_sys_mknodat fs/namei.c:4022 [inline] __se_sys_mknodat fs/namei.c:4019 [inline] __x64_sys_mknodat+0xa5/0xc0 fs/namei.c:4019 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #1 (sb_writers#24){.+.+}-{0:0}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1811 [inline] sb_start_write+0x4f/0x1c0 include/linux/fs.h:1881 mnt_want_write_file+0x5a/0x1f0 fs/namespace.c:421 reiserfs_ioctl+0x170/0x340 fs/reiserfs/ioctl.c:103 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #0 (&sbi->lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain+0x1649/0x5930 kernel/locking/lockdep.c:3788 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27 reiserfs_lookup+0x15c/0x4b0 fs/reiserfs/namei.c:364 lookup_one_qstr_excl+0x117/0x240 fs/namei.c:1563 filename_create+0x293/0x530 fs/namei.c:3836 do_mknodat+0x176/0x690 fs/namei.c:3981 __do_sys_mknodat fs/namei.c:4022 [inline] __se_sys_mknodat fs/namei.c:4019 [inline] __x64_sys_mknodat+0xa5/0xc0 fs/namei.c:4019 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 other info that might help us debug this: Chain exists of: &sbi->lock --> sb_writers#24 --> &type->i_mutex_dir_key#19/1 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&type->i_mutex_dir_key#19/1); lock(sb_writers#24); lock(&type->i_mutex_dir_key#19/1); lock(&sbi->lock); *** DEADLOCK *** 2 locks held by syz.0.334/5206: #0: ffff88801b1be460 (sb_writers#24){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377 #1: ffff888067f182e0 (&type->i_mutex_dir_key#19/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline] #1: ffff888067f182e0 (&type->i_mutex_dir_key#19/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3835 stack backtrace: CPU: 1 PID: 5206 Comm: syz.0.334 Not tainted 5.15.179-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106 check_noncircular+0x2f8/0x3b0 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+0x1649/0x5930 kernel/locking/lockdep.c:3788 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27 reiserfs_lookup+0x15c/0x4b0 fs/reiserfs/namei.c:364 lookup_one_qstr_excl+0x117/0x240 fs/namei.c:1563 filename_create+0x293/0x530 fs/namei.c:3836 do_mknodat+0x176/0x690 fs/namei.c:3981 __do_sys_mknodat fs/namei.c:4022 [inline] __se_sys_mknodat fs/namei.c:4019 [inline] __x64_sys_mknodat+0xa5/0xc0 fs/namei.c:4019 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 RIP: 0033:0x7f66effa6169 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f66ede0f038 EFLAGS: 00000246 ORIG_RAX: 0000000000000103 RAX: ffffffffffffffda RBX: 00007f66f01befa0 RCX: 00007f66effa6169 RDX: 0000000000002000 RSI: 0000400000000340 RDI: 0000000000000004 RBP: 00007f66f00272a0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000103 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f66f01befa0 R15: 00007ffd9fbd97e8