======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.7.3732/20929 is trying to acquire lock:
ffff88802bf7cee0 (&oi->ip_alloc_sem){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xb6/0x320

but task is already holding lock:
ffff88802bf7cf78 (&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_create+0x1a5/0x440
       path_openat+0x14f4/0x3830
       do_filp_open+0x1fa/0x410
       do_sys_openat2+0x121/0x1c0
       __x64_sys_openat+0x138/0x170
       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#4){.+.+}-{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
       __x64_sys_pwrite64+0x193/0x220
       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_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:
  &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 ***

2 locks held by syz.7.3732/20929:
 #0: ffff88802bf7d240 (&sb->s_type->i_mutex_key#41){+.+.}-{4:4}, at: do_truncate+0x171/0x220
 #1: ffff88802bf7cf78 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xa4/0x320

stack backtrace:
CPU: 0 UID: 0 PID: 20929 Comm: syz.7.3732 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:0x7fc001e4f920
Code: Unable to access opcode bytes at 0x7fc001e4f8f6.
RSP: 002b:00007fc002e0d0f8 EFLAGS: 00010206
RAX: 0000000000000000 RBX: 00007fc0021c6090 RCX: 00007fc001f8ebe9
RDX: 00007fc002e0d100 RSI: 00007fc002e0d230 RDI: 000000000000000b
RBP: 00007fc002011e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 00007fc0021c6128 R14: 00007fc0021c6090 R15: 00007ffd17722fd8
 </TASK>
