REISERFS (device loop4): Using tea hash to sort names REISERFS warning (device loop4): vs-13060 reiserfs_update_sd_size: stat data of object [1 2 0x0 SD] (nlink == 1) not found (pos 2) REISERFS (device loop4): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected 6.6.0-rc3-syzkaller-00055-g9ed22ae6be81 #0 Not tainted ------------------------------------------------------ syz-executor.4/15281 is trying to acquire lock: ffff8880359bf090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27 but task is already holding lock: ffff8880849796c0 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:837 [inline] ffff8880849796c0 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: filename_create+0x1c2/0x530 fs/namei.c:3889 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}: down_write_nested+0x97/0x200 kernel/locking/rwsem.c:1689 inode_lock_nested include/linux/fs.h:837 [inline] filename_create+0x1c2/0x530 fs/namei.c:3889 do_mkdirat+0xb3/0x330 fs/namei.c:4135 __do_sys_mkdirat fs/namei.c:4158 [inline] __se_sys_mkdirat fs/namei.c:4156 [inline] __x64_sys_mkdirat+0x115/0x170 fs/namei.c:4156 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #1 (sb_writers#33){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1571 [inline] sb_start_write include/linux/fs.h:1646 [inline] mnt_want_write_file+0x98/0x600 fs/namespace.c:447 reiserfs_ioctl+0x194/0x2e0 fs/reiserfs/ioctl.c:103 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:871 [inline] __se_sys_ioctl fs/ioctl.c:857 [inline] __x64_sys_ioctl+0x18f/0x210 fs/ioctl.c:857 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&sbi->lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3868 [inline] __lock_acquire+0x2e3d/0x5de0 kernel/locking/lockdep.c:5136 lock_acquire kernel/locking/lockdep.c:5753 [inline] lock_acquire+0x1ae/0x510 kernel/locking/lockdep.c:5718 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x181/0x1340 kernel/locking/mutex.c:747 reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27 reiserfs_lookup+0x184/0x690 fs/reiserfs/namei.c:364 lookup_one_qstr_excl+0x116/0x180 fs/namei.c:1608 filename_create+0x1ed/0x530 fs/namei.c:3890 do_mkdirat+0xb3/0x330 fs/namei.c:4135 __do_sys_mkdirat fs/namei.c:4158 [inline] __se_sys_mkdirat fs/namei.c:4156 [inline] __x64_sys_mkdirat+0x115/0x170 fs/namei.c:4156 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Chain exists of: &sbi->lock --> sb_writers#33 --> &type->i_mutex_dir_key#20/1 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&type->i_mutex_dir_key#20/1); lock(sb_writers#33); lock(&type->i_mutex_dir_key#20/1); lock(&sbi->lock); *** DEADLOCK *** 2 locks held by syz-executor.4/15281: #0: ffff888031e68410 (sb_writers#33){.+.+}-{0:0}, at: filename_create+0x10d/0x530 fs/namei.c:3882 #1: ffff8880849796c0 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:837 [inline] #1: ffff8880849796c0 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: filename_create+0x1c2/0x530 fs/namei.c:3889 stack backtrace: CPU: 0 PID: 15281 Comm: syz-executor.4 Not tainted 6.6.0-rc3-syzkaller-00055-g9ed22ae6be81 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106 check_noncircular+0x311/0x3f0 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3868 [inline] __lock_acquire+0x2e3d/0x5de0 kernel/locking/lockdep.c:5136 lock_acquire kernel/locking/lockdep.c:5753 [inline] lock_acquire+0x1ae/0x510 kernel/locking/lockdep.c:5718 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x181/0x1340 kernel/locking/mutex.c:747 reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27 reiserfs_lookup+0x184/0x690 fs/reiserfs/namei.c:364 lookup_one_qstr_excl+0x116/0x180 fs/namei.c:1608 filename_create+0x1ed/0x530 fs/namei.c:3890 do_mkdirat+0xb3/0x330 fs/namei.c:4135 __do_sys_mkdirat fs/namei.c:4158 [inline] __se_sys_mkdirat fs/namei.c:4156 [inline] __x64_sys_mkdirat+0x115/0x170 fs/namei.c:4156 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f93fee7cae9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f93ffcc40c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 00007f93fef9bf80 RCX: 00007f93fee7cae9 RDX: 0000000000000000 RSI: 0000000020000180 RDI: ffffffffffffff9c RBP: 00007f93feec847a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f93fef9bf80 R15: 00007ffc475e58e8