REISERFS (device loop5): Remounting filesystem read-only REISERFS error (device loop5): vs-13080 reiserfs_new_directory: i/o failure occurred creating new directory ====================================================== WARNING: possible circular locking dependency detected 5.15.187-syzkaller #0 Not tainted ------------------------------------------------------ syz.5.962/9242 is trying to acquire lock: ffff888076b93e80 (&type->i_mutex_dir_key#22/3){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline] ffff888076b93e80 (&type->i_mutex_dir_key#22/3){+.+.}-{3:3}, at: open_xa_root fs/reiserfs/xattr.c:127 [inline] ffff888076b93e80 (&type->i_mutex_dir_key#22/3){+.+.}-{3:3}, at: open_xa_dir+0x11d/0x6b0 fs/reiserfs/xattr.c:152 but task is already holding lock: ffff88805fc63090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock_nested+0x5c/0xd0 fs/reiserfs/lock.c:78 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&sbi->lock){+.+.}-{3:3}: __mutex_lock_common+0x1eb/0x2390 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+0x75/0xd0 fs/reiserfs/lock.c:27 reiserfs_mkdir+0x30c/0x970 fs/reiserfs/namei.c:831 xattr_mkdir fs/reiserfs/xattr.c:76 [inline] open_xa_root fs/reiserfs/xattr.c:136 [inline] open_xa_dir+0x318/0x6b0 fs/reiserfs/xattr.c:152 xattr_lookup+0x22/0x2a0 fs/reiserfs/xattr.c:395 reiserfs_xattr_set_handle+0xf4/0xf20 fs/reiserfs/xattr.c:540 reiserfs_xattr_set+0x435/0x550 fs/reiserfs/xattr.c:640 __vfs_setxattr+0x3e0/0x420 fs/xattr.c:182 __vfs_setxattr_noperm+0x129/0x5e0 fs/xattr.c:216 vfs_setxattr+0x168/0x2f0 fs/xattr.c:303 do_setxattr fs/xattr.c:588 [inline] setxattr+0x2da/0x300 fs/xattr.c:611 path_setxattr+0x142/0x280 fs/xattr.c:630 __do_sys_setxattr fs/xattr.c:646 [inline] __se_sys_setxattr fs/xattr.c:642 [inline] __x64_sys_setxattr+0xb7/0xd0 fs/xattr.c:642 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 (&type->i_mutex_dir_key#22/3){+.+.}-{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+0x2c33/0x7c60 kernel/locking/lockdep.c:5012 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623 down_write_nested+0x3b/0x60 kernel/locking/rwsem.c:1667 inode_lock_nested include/linux/fs.h:822 [inline] open_xa_root fs/reiserfs/xattr.c:127 [inline] open_xa_dir+0x11d/0x6b0 fs/reiserfs/xattr.c:152 reiserfs_for_each_xattr+0x174/0x7b0 fs/reiserfs/xattr.c:252 reiserfs_delete_xattrs+0x1c/0x80 fs/reiserfs/xattr.c:364 reiserfs_evict_inode+0x221/0x490 fs/reiserfs/inode.c:53 evict+0x485/0x870 fs/inode.c:647 reiserfs_new_inode+0x5c8/0x1860 fs/reiserfs/inode.c:2164 reiserfs_mkdir+0x557/0x970 fs/reiserfs/namei.c:845 vfs_mkdir+0x387/0x570 fs/namei.c:4065 do_mkdirat+0x1d7/0x5a0 fs/namei.c:4090 __do_sys_mkdirat fs/namei.c:4105 [inline] __se_sys_mkdirat fs/namei.c:4103 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4103 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: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->lock); lock(&type->i_mutex_dir_key#22/3); lock(&sbi->lock); lock(&type->i_mutex_dir_key#22/3); *** DEADLOCK *** 3 locks held by syz.5.962/9242: #0: ffff88814c654460 (sb_writers#36){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377 #1: ffff888076b937e0 (&type->i_mutex_dir_key#22/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline] #1: ffff888076b937e0 (&type->i_mutex_dir_key#22/1){+.+.}-{3:3}, at: filename_create+0x1f2/0x450 fs/namei.c:3835 #2: ffff88805fc63090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock_nested+0x5c/0xd0 fs/reiserfs/lock.c:78 stack backtrace: CPU: 1 PID: 9242 Comm: syz.5.962 Not tainted 5.15.187-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106 check_noncircular+0x274/0x310 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+0x2c33/0x7c60 kernel/locking/lockdep.c:5012 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623 down_write_nested+0x3b/0x60 kernel/locking/rwsem.c:1667 inode_lock_nested include/linux/fs.h:822 [inline] open_xa_root fs/reiserfs/xattr.c:127 [inline] open_xa_dir+0x11d/0x6b0 fs/reiserfs/xattr.c:152 reiserfs_for_each_xattr+0x174/0x7b0 fs/reiserfs/xattr.c:252 reiserfs_delete_xattrs+0x1c/0x80 fs/reiserfs/xattr.c:364 reiserfs_evict_inode+0x221/0x490 fs/reiserfs/inode.c:53 evict+0x485/0x870 fs/inode.c:647 reiserfs_new_inode+0x5c8/0x1860 fs/reiserfs/inode.c:2164 reiserfs_mkdir+0x557/0x970 fs/reiserfs/namei.c:845 vfs_mkdir+0x387/0x570 fs/namei.c:4065 do_mkdirat+0x1d7/0x5a0 fs/namei.c:4090 __do_sys_mkdirat fs/namei.c:4105 [inline] __se_sys_mkdirat fs/namei.c:4103 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4103 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:0x7faef26d8197 Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 02 01 00 00 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:00007faef0540e68 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 00007faef0540ef0 RCX: 00007faef26d8197 RDX: 00000000000001ff RSI: 00002000000016c0 RDI: 00000000ffffff9c RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00002000000016c0 R13: 00007faef0540eb0 R14: 0000000000000000 R15: 0000000000000000