loop1: detected capacity change from 0 to 32768
ocfs2: Mounting device (7,1) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.1.10323/16048 is trying to acquire lock:
ffff888124804ee0 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xb6/0x320

but task is already holding lock:
ffff888124804f78 (&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:

-> #2 (&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

-> #1 (jbd2_handle){++++}-{0:0}:
       lock_acquire+0x120/0x360
       jbd2_log_wait_commit+0x17c/0x4a0
       ocfs2_try_to_free_truncate_log+0x317/0x360
       ocfs2_write_begin_nolock+0x3143/0x4340
       ocfs2_write_begin+0x1bb/0x310
       generic_perform_write+0x2c5/0x900
       ocfs2_file_write_iter+0x157a/0x1d10
       vfs_write+0x5c9/0xb30
       __x64_sys_pwrite64+0x193/0x220
       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_truncate_file+0xda0/0x1420
       ocfs2_setattr+0x1520/0x1b40
       notify_change+0xb36/0xe40
       do_truncate+0x1a4/0x220
       coredump_file+0x7cb/0xaf0
       vfs_coredump+0x1688/0x2a50
       get_signal+0x1109/0x1340
       arch_do_signal_or_restart+0x9a/0x750
       exit_to_user_mode_loop+0x75/0x110
       do_syscall_64+0x2bd/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 ***

2 locks held by syz.1.10323/16048:
 #0: ffff888124805240 (&sb->s_type->i_mutex_key#33){+.+.}-{4:4}, at: do_truncate+0x171/0x220
 #1: ffff888124804f78 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xa4/0x320

stack backtrace:
CPU: 1 UID: 0 PID: 16048 Comm: syz.1.10323 Not tainted syzkaller #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_truncate_file+0xda0/0x1420
 ocfs2_setattr+0x1520/0x1b40
 notify_change+0xb36/0xe40
 do_truncate+0x1a4/0x220
 coredump_file+0x7cb/0xaf0
 vfs_coredump+0x1688/0x2a50
 get_signal+0x1109/0x1340
 arch_do_signal_or_restart+0x9a/0x750
 exit_to_user_mode_loop+0x75/0x110
 do_syscall_64+0x2bd/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f563824f980
Code: 48 c1 e8 12 83 e0 01 88 15 72 5d eb 00 88 05 6f 5d eb 00 c3 50 48 8d 35 c9 24 1c 00 48 8d 3d cf 24 1c 00 31 c0 e8 20 f7 ff ff <53> 89 fb 48 83 ec 10 64 8b 04 25 94 ff ff ff 85 c0 74 2a 89 fe 31
RSP: 002b:00007f5639195c78 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: 0000000000000000 RBX: 00007f56385d5fa8 RCX: 00007f563838ec29
RDX: 00007f5639195c80 RSI: 00007f5639195db0 RDI: 000000000000000b
RBP: 00007f56385d5fa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f56385d6038 R14: 00007ffc4a8b7670 R15: 00007ffc4a8b7758
 </TASK>
