======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.1.2594/14094 is trying to acquire lock:
ffff88811ce8ebe0 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xb6/0x320

but task is already holding lock:
ffff88811ce8ec78 (&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_mkdir+0x6c/0x80
       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_shutdown_local_alloc+0x200/0xa10
       ocfs2_dismount_volume+0x201/0x8d0
       generic_shutdown_super+0x135/0x2c0
       kill_block_super+0x44/0x90
       deactivate_locked_super+0xbc/0x130
       cleanup_mnt+0x425/0x4c0
       task_work_run+0x1d4/0x260
       exit_to_user_mode_loop+0xec/0x110
       do_syscall_64+0x2bd/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_shutdown_local_alloc+0x200/0xa10
       ocfs2_dismount_volume+0x201/0x8d0
       generic_shutdown_super+0x135/0x2c0
       kill_block_super+0x44/0x90
       deactivate_locked_super+0xbc/0x130
       cleanup_mnt+0x425/0x4c0
       task_work_run+0x1d4/0x260
       exit_to_user_mode_loop+0xec/0x110
       do_syscall_64+0x2bd/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (sb_internal#6){.+.+}-{0:0}:
       lock_acquire+0x120/0x360
       ocfs2_start_trans+0x26b/0x6d0
       ocfs2_write_begin_nolock+0x1ca6/0x4340
       ocfs2_write_begin+0x1bb/0x310
       generic_perform_write+0x2c5/0x900
       ocfs2_file_write_iter+0x157a/0x1d10
       vfs_write+0x5c9/0xb30
       ksys_write+0x145/0x250
       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
       irqentry_exit_to_user_mode+0x81/0x120
       exc_page_fault+0x9f/0xf0
       asm_exc_page_fault+0x26/0x30

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.2594/14094:
 #0: ffff88811ce8ef40 (&sb->s_type->i_mutex_key#44){+.+.}-{4:4}, at: do_truncate+0x171/0x220
 #1: ffff88811ce8ec78 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xa4/0x320

stack backtrace:
CPU: 0 UID: 0 PID: 14094 Comm: syz.1.2594 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
 irqentry_exit_to_user_mode+0x81/0x120
 exc_page_fault+0x9f/0xf0
 asm_exc_page_fault+0x26/0x30
RIP: 0033:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 002b:0000200000000438 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007f70705c5fa0 RCX: 00007f707038ebe9
RDX: 0000200000000000 RSI: 0000200000000430 RDI: 0000000008000000
RBP: 00007f7070411e19 R08: 0000200000000200 R09: 0000200000000200
R10: 00002000000000c0 R11: 0000000000000206 R12: 0000000000000000
R13: 00007f70705c6038 R14: 00007f70705c5fa0 R15: 00007ffcde60c228
 </TASK>
ocfs2: Unmounting device (7,1) on (node local)
syz.1.2594 (14094) used greatest stack depth: 16712 bytes left
