ocfs2: Mounting device (7,1) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
6.17.0-rc1-syzkaller-00036-gdfc0f6373094 #0 Not tainted
------------------------------------------------------
syz.1.8022/28814 is trying to acquire lock:
ffff8880315cdd60 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xb6/0x320

but task is already holding lock:
ffff8880315cddf8 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xa4/0x320

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (&oi->ip_xattr_sem){++++}-{4:4}:
       lock_acquire+0x120/0x360
       down_read+0x46/0x2e0
       ocfs2_init_acl+0x2f9/0x720
       ocfs2_mknod+0x1321/0x2050
       ocfs2_mkdir+0x191/0x440
       vfs_mkdir+0x306/0x510
       do_mkdirat+0x247/0x590
       __x64_sys_mkdirat+0x87/0xa0
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #3 (jbd2_handle){++++}-{0:0}:
       lock_acquire+0x120/0x360
       start_this_handle+0x1fa7/0x21c0
       jbd2__journal_start+0x2c1/0x5b0
       jbd2_journal_start+0x2a/0x40
       ocfs2_start_trans+0x376/0x6d0
       ocfs2_reserve_local_alloc_bits+0xb04/0x24e0
       ocfs2_reserve_clusters_with_limit+0x1be/0xba0
       ocfs2_extend_dir+0x701/0x4870
       ocfs2_prepare_dir_for_insert+0x2fe8/0x5450
       ocfs2_mknod+0x819/0x2050
       ocfs2_create+0x1a5/0x440
       vfs_create+0x24e/0x400
       do_mknodat+0x3c6/0x4d0
       __x64_sys_mknod+0x8c/0xa0
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&journal->j_trans_barrier){.+.+}-{4:4}:
       lock_acquire+0x120/0x360
       down_read+0x46/0x2e0
       ocfs2_start_trans+0x36a/0x6d0
       ocfs2_reserve_local_alloc_bits+0xb04/0x24e0
       ocfs2_reserve_clusters_with_limit+0x1be/0xba0
       ocfs2_extend_dir+0x701/0x4870
       ocfs2_prepare_dir_for_insert+0x2fe8/0x5450
       ocfs2_mknod+0x819/0x2050
       ocfs2_create+0x1a5/0x440
       vfs_create+0x24e/0x400
       do_mknodat+0x3c6/0x4d0
       __x64_sys_mknod+0x8c/0xa0
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (sb_internal#5){.+.+}-{0:0}:
       lock_acquire+0x120/0x360
       ocfs2_start_trans+0x26b/0x6d0
       ocfs2_extend_dir+0x10a8/0x4870
       ocfs2_prepare_dir_for_insert+0x3d7b/0x5450
       ocfs2_rename+0x190a/0x3940
       vfs_rename+0xbda/0xf00
       do_renameat2+0x6ce/0xa80
       __x64_sys_rename+0x82/0x90
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}:
       validate_chain+0xb9b/0x2140
       __lock_acquire+0xab9/0xd20
       lock_acquire+0x120/0x360
       down_write+0x96/0x1f0
       ocfs2_try_remove_refcount_tree+0xb6/0x320
       ocfs2_xattr_set+0x595/0x11f0
       ocfs2_set_acl+0x701/0x7b0
       ocfs2_iop_set_acl+0x1aa/0x2a0
       vfs_set_acl+0x887/0xb00
       filename_setxattr+0x2e0/0x600
       path_setxattrat+0x364/0x3a0
       __x64_sys_setxattr+0xbc/0xe0
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &ocfs2_file_ip_alloc_sem_key --> jbd2_handle --> &oi->ip_xattr_sem

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&oi->ip_xattr_sem);
                               lock(jbd2_handle);
                               lock(&oi->ip_xattr_sem);
  lock(&ocfs2_file_ip_alloc_sem_key);

 *** DEADLOCK ***

3 locks held by syz.1.8022/28814:
 #0: ffff8881058bc428 (sb_writers#30){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff8880315ce0c0 (&type->i_mutex_dir_key#27){++++}-{4:4}, at: vfs_set_acl+0x3cd/0xb00
 #2: ffff8880315cddf8 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xa4/0x320

stack backtrace:
CPU: 0 UID: 0 PID: 28814 Comm: syz.1.8022 Not tainted 6.17.0-rc1-syzkaller-00036-gdfc0f6373094 #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250
 print_circular_bug+0x2ee/0x310
 check_noncircular+0x134/0x160
 validate_chain+0xb9b/0x2140
 __lock_acquire+0xab9/0xd20
 lock_acquire+0x120/0x360
 down_write+0x96/0x1f0
 ocfs2_try_remove_refcount_tree+0xb6/0x320
 ocfs2_xattr_set+0x595/0x11f0
 ocfs2_set_acl+0x701/0x7b0
 ocfs2_iop_set_acl+0x1aa/0x2a0
 vfs_set_acl+0x887/0xb00
 filename_setxattr+0x2e0/0x600
 path_setxattrat+0x364/0x3a0
 __x64_sys_setxattr+0xbc/0xe0
 do_syscall_64+0xfa/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fea3998ebe9
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:00007fea3a89c038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007fea39bb5fa0 RCX: 00007fea3998ebe9
RDX: 0000000000000000 RSI: 0000200000002a40 RDI: 0000200000002a00
RBP: 00007fea39a11e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fea39bb6038 R14: 00007fea39bb5fa0 R15: 00007ffff064eda8
 </TASK>
