JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,4) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
6.17.0-rc1-syzkaller-00036-gdfc0f6373094-dirty #0 Not tainted
------------------------------------------------------
syz.4.2603/13001 is trying to acquire lock:
ffff888112eca360 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xb6/0x320

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

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

-> #4 (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

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

-> #2 (sb_internal#3){.+.+}-{0:0}:
       lock_acquire+0x120/0x360
       ocfs2_start_trans+0x26b/0x6d0
       ocfs2_create_refcount_tree+0x349/0x1250
       ocfs2_reflink_remap_blocks+0x2ea/0x1930
       ocfs2_remap_file_range+0x4b7/0x730
       vfs_clone_file_range+0x42c/0x7a0
       do_vfs_ioctl+0xd2b/0x1430
       __se_sys_ioctl+0x82/0x170
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&ocfs2_sysfile_lock_key[EXTENT_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}:
       lock_acquire+0x120/0x360
       down_write+0x96/0x1f0
       ocfs2_reserve_suballoc_bits+0x15e/0x4640
       ocfs2_reserve_new_metadata_blocks+0x403/0x940
       ocfs2_lock_allocators+0x29e/0x5c0
       ocfs2_extend_allocation+0x39b/0x17a0
       ocfs2_allocate_unwritten_extents+0x2e9/0x7b0
       __ocfs2_change_file_space+0x901/0xe80
       ocfs2_fallocate+0x1f5/0x240
       vfs_fallocate+0x669/0x7e0
       __x64_sys_fallocate+0xc0/0x110
       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.4.2603/13001:
 #0: ffff88812735e428 (sb_writers#22){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff888112eca6c0 (&type->i_mutex_dir_key#25){++++}-{4:4}, at: vfs_set_acl+0x3cd/0xb00
 #2: ffff888112eca3f8 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_try_remove_refcount_tree+0xa4/0x320

stack backtrace:
CPU: 0 UID: 0 PID: 13001 Comm: syz.4.2603 Not tainted 6.17.0-rc1-syzkaller-00036-gdfc0f6373094-dirty #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:0x7f281718ebe9
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:00007f28180a0038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007f28173b5fa0 RCX: 00007f281718ebe9
RDX: 0000000000000000 RSI: 0000200000002a40 RDI: 0000200000002a00
RBP: 00007f2817211e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f28173b6038 R14: 00007f28173b5fa0 R15: 00007ffc8d4a20d8
 </TASK>
