REISERFS warning (device loop2): reiserfs-15100 reiserfs_get_unused_objectid: no more object ids
REISERFS warning (device loop2): jdm-20006 create_privroot: xattrs/ACLs enabled and couldn't find/create .reiserfs_priv. Failing mount.
======================================================
WARNING: possible circular locking dependency detected
6.5.0-rc1-syzkaller-00248-gb6e6cc1f78c7 #0 Not tainted
------------------------------------------------------
syz-executor.2/8002 is trying to acquire lock:
ffff88803fc002e0 (&type->i_mutex_dir_key#16){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:771 [inline]
ffff88803fc002e0 (&type->i_mutex_dir_key#16){+.+.}-{3:3}, at: vfs_fileattr_set+0x139/0xd40 fs/ioctl.c:681

but task is already holding lock:
ffff888022d30410 (sb_writers#27){.+.+}-{0:0}, at: mnt_want_write_file+0x61/0x200 fs/namespace.c:447

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (sb_writers#27){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1494 [inline]
       sb_start_write+0x4d/0x1c0 include/linux/fs.h:1569
       mnt_want_write_file+0x61/0x200 fs/namespace.c:447
       reiserfs_ioctl+0x177/0x350 fs/reiserfs/ioctl.c:103
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #1 (&sbi->lock){+.+.}-{3:3}:
       __mutex_lock_common+0x1d8/0x2530 kernel/locking/mutex.c:603
       __mutex_lock kernel/locking/mutex.c:747 [inline]
       mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
       reiserfs_write_lock+0x7a/0xd0 fs/reiserfs/lock.c:27
       reiserfs_lookup+0x162/0x580 fs/reiserfs/namei.c:364
       __lookup_slow+0x282/0x3e0 fs/namei.c:1690
       lookup_one_len+0x18b/0x2d0 fs/namei.c:2742
       reiserfs_lookup_privroot+0x89/0x180 fs/reiserfs/xattr.c:976
       reiserfs_fill_super+0x195b/0x2620 fs/reiserfs/super.c:2192
       mount_bdev+0x276/0x3b0 fs/super.c:1391
       legacy_get_tree+0xef/0x190 fs/fs_context.c:611
       vfs_get_tree+0x8c/0x270 fs/super.c:1519
       do_new_mount+0x28f/0xae0 fs/namespace.c:3335
       do_mount fs/namespace.c:3675 [inline]
       __do_sys_mount fs/namespace.c:3884 [inline]
       __se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3861
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (&type->i_mutex_dir_key#16){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3142 [inline]
       check_prevs_add kernel/locking/lockdep.c:3261 [inline]
       validate_chain kernel/locking/lockdep.c:3876 [inline]
       __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5144
       lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5761
       down_write+0x3a/0x50 kernel/locking/rwsem.c:1573
       inode_lock include/linux/fs.h:771 [inline]
       vfs_fileattr_set+0x139/0xd40 fs/ioctl.c:681
       ioctl_fssetxattr fs/ioctl.c:758 [inline]
       do_vfs_ioctl+0x1881/0x2b30 fs/ioctl.c:845
       __do_sys_ioctl fs/ioctl.c:868 [inline]
       __se_sys_ioctl+0x81/0x170 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

other info that might help us debug this:

Chain exists of:
  &type->i_mutex_dir_key#16 --> &sbi->lock --> sb_writers#27

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(sb_writers#27);
                               lock(&sbi->lock);
                               lock(sb_writers#27);
  lock(&type->i_mutex_dir_key#16);

 *** DEADLOCK ***

1 lock held by syz-executor.2/8002:
 #0: ffff888022d30410 (sb_writers#27){.+.+}-{0:0}, at: mnt_want_write_file+0x61/0x200 fs/namespace.c:447

stack backtrace:
CPU: 0 PID: 8002 Comm: syz-executor.2 Not tainted 6.5.0-rc1-syzkaller-00248-gb6e6cc1f78c7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 check_noncircular+0x375/0x4a0 kernel/locking/lockdep.c:2195
 check_prev_add kernel/locking/lockdep.c:3142 [inline]
 check_prevs_add kernel/locking/lockdep.c:3261 [inline]
 validate_chain kernel/locking/lockdep.c:3876 [inline]
 __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5144
 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5761
 down_write+0x3a/0x50 kernel/locking/rwsem.c:1573
 inode_lock include/linux/fs.h:771 [inline]
 vfs_fileattr_set+0x139/0xd40 fs/ioctl.c:681
 ioctl_fssetxattr fs/ioctl.c:758 [inline]
 do_vfs_ioctl+0x1881/0x2b30 fs/ioctl.c:845
 __do_sys_ioctl fs/ioctl.c:868 [inline]
 __se_sys_ioctl+0x81/0x170 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f8d69e7cb29
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:00007f8d6ac1b0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f8d69f9bf80 RCX: 00007f8d69e7cb29
RDX: 0000000020000000 RSI: 00000000401c5820 RDI: 0000000000000005
RBP: 00007f8d69ec847a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f8d69f9bf80 R15: 00007fffdb0fae38
 </TASK>