REISERFS (device loop0): Remounting filesystem read-only REISERFS error (device loop0): vs-13080 reiserfs_new_directory: i/o failure occurred creating new directory ============================================ WARNING: possible recursive locking detected 5.15.187-syzkaller #0 Not tainted -------------------------------------------- syz.0.451/6746 is trying to acquire lock: ffff8880550fb140 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline] ffff8880550fb140 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: open_xa_root fs/reiserfs/xattr.c:127 [inline] ffff8880550fb140 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: open_xa_dir+0x11d/0x6b0 fs/reiserfs/xattr.c:152 but task is already holding lock: ffff888060efaaa0 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline] ffff888060efaaa0 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: open_xa_dir+0x421/0x6b0 fs/reiserfs/xattr.c:160 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&type->i_mutex_dir_key#9/3); lock(&type->i_mutex_dir_key#9/3); *** DEADLOCK *** May be due to missing lock nesting notation 4 locks held by syz.0.451/6746: #0: ffff888058568460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write_file+0x5c/0x200 fs/namespace.c:421 #1: ffff8880550fb7e0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline] #1: ffff8880550fb7e0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: vfs_setxattr+0x141/0x2f0 fs/xattr.c:302 #2: ffff888060efaaa0 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline] #2: ffff888060efaaa0 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: open_xa_dir+0x421/0x6b0 fs/reiserfs/xattr.c:160 #3: ffff88802adde090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock_nested+0x5c/0xd0 fs/reiserfs/lock.c:78 stack backtrace: CPU: 1 PID: 6746 Comm: syz.0.451 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 __lock_acquire+0x1227/0x7c60 kernel/locking/lockdep.c:-1 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 xattr_mkdir fs/reiserfs/xattr.c:76 [inline] open_xa_dir+0x5af/0x6b0 fs/reiserfs/xattr.c:167 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 __do_sys_fsetxattr fs/xattr.c:667 [inline] __se_sys_fsetxattr+0x15e/0x1d0 fs/xattr.c:656 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:0x7fa8f6f78929 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:00007fa8f4dbf038 EFLAGS: 00000246 ORIG_RAX: 00000000000000be RAX: ffffffffffffffda RBX: 00007fa8f71a0080 RCX: 00007fa8f6f78929 RDX: 0000200000000240 RSI: 0000200000000180 RDI: 0000000000000004 RBP: 00007fa8f6ffab39 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000014 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000001 R14: 00007fa8f71a0080 R15: 00007fff76158278