loop0: detected capacity change from 0 to 32768
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
6.16.0-syzkaller-11895-gcca7a0aae895 #0 Not tainted
------------------------------------------------------
syz.0.146/6346 is trying to acquire lock:
ffff8881149bcee0 (&oi->ip_alloc_sem){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xb6/0x320

but task is already holding lock:
ffff8881149bcf78 (&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_suballoc_bits+0x711/0x4640
       ocfs2_reserve_new_metadata_blocks+0x403/0x940
       ocfs2_extend_dir+0xc76/0x4870
       ocfs2_prepare_dir_for_insert+0x2fe8/0x5450
       ocfs2_symlink+0xaa4/0x23e0
       vfs_symlink+0x143/0x2f0
       do_symlinkat+0x1b1/0x3f0
       __x64_sys_symlink+0x7a/0x90
       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_suballoc_bits+0x711/0x4640
       ocfs2_reserve_new_metadata_blocks+0x403/0x940
       ocfs2_extend_dir+0xc76/0x4870
       ocfs2_prepare_dir_for_insert+0x2fe8/0x5450
       ocfs2_symlink+0xaa4/0x23e0
       vfs_symlink+0x143/0x2f0
       do_symlinkat+0x1b1/0x3f0
       __x64_sys_symlink+0x7a/0x90
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (sb_internal#2){.+.+}-{0:0}:
       reacquire_held_locks+0x127/0x1d0
       lock_release+0x1b4/0x3e0
       up_write+0x2d/0x420
       ocfs2_free_alloc_context+0x97/0x1a0
       ocfs2_write_begin_nolock+0x4296/0x4340
       ocfs2_write_begin+0x1bb/0x310
       generic_perform_write+0x2c5/0x900
       ocfs2_file_write_iter+0x157a/0x1d10
       vfs_write+0x54b/0xa90
       ksys_write+0x145/0x250
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&oi->ip_alloc_sem){++++}-{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:
  &oi->ip_alloc_sem --> 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(&oi->ip_alloc_sem);

 *** DEADLOCK ***

3 locks held by syz.0.146/6346:
 #0: ffff88810a188428 (sb_writers#19){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff8881149bd240 (&sb->s_type->i_mutex_key#25){+.+.}-{4:4}, at: vfs_set_acl+0x3cd/0xb00
 #2: ffff8881149bcf78 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xa4/0x320

stack backtrace:
CPU: 1 UID: 0 PID: 6346 Comm: syz.0.146 Not tainted 6.16.0-syzkaller-11895-gcca7a0aae895 #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:0x7fa9bc78ebe9
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:00007fa9bd525038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007fa9bc9b5fa0 RCX: 00007fa9bc78ebe9
RDX: 0000000000000000 RSI: 0000200000002b80 RDI: 0000200000000140
RBP: 00007fa9bc811e19 R08: 0000000000000003 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa9bc9b6038 R14: 00007fa9bc9b5fa0 R15: 00007fff05a255f8
 </TASK>
syz.0.146 (6346) used greatest stack depth: 19272 bytes left
