JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,2) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.2.4299/23047 is trying to acquire lock:
ffff8881bb7fe8e8 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_init_acl+0x2fd/0x7e0

but task is already holding lock:
ffff88816edc78e0 (&journal->j_trans_barrier){.+.+}-{4:4}, at: ocfs2_start_trans+0x3ab/0x700

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (&journal->j_trans_barrier){.+.+}-{4:4}:
       down_read+0x47/0x2e0
       ocfs2_start_trans+0x3ab/0x700
       ocfs2_setattr+0xcc6/0x1ca0
       notify_change+0xc1a/0xf40
       chown_common+0x466/0x6b0
       do_fchownat+0x14c/0x250
       __x64_sys_lchown+0x85/0xa0
       do_syscall_64+0x174/0x580
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #3 (sb_internal#6){.+.+}-{0:0}:
       ocfs2_start_trans+0x2ac/0x700
       ocfs2_mknod+0x1181/0x2260
       ocfs2_mkdir+0x181/0x460
       vfs_mkdir+0x413/0x630
       filename_mkdirat+0x285/0x510
       __se_sys_mkdirat+0x35/0x150
       do_syscall_64+0x174/0x580
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&ocfs2_sysfile_lock_key[LOCAL_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}:
       down_write+0x96/0x200
       ocfs2_reserve_local_alloc_bits+0x11f/0x2660
       ocfs2_reserve_clusters_with_limit+0x1b9/0xc20
       ocfs2_mknod+0x111f/0x2260
       ocfs2_mkdir+0x181/0x460
       vfs_mkdir+0x413/0x630
       filename_mkdirat+0x285/0x510
       __se_sys_mkdirat+0x35/0x150
       do_syscall_64+0x174/0x580
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&ocfs2_sysfile_lock_key[EXTENT_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}:
       down_write+0x96/0x200
       ocfs2_reserve_suballoc_bits+0x16d/0x4840
       ocfs2_reserve_new_metadata_blocks+0x415/0x9a0
       ocfs2_init_xattr_set_ctxt+0x2f5/0x760
       ocfs2_xattr_set+0xc42/0x13e0
       __vfs_setxattr+0x43c/0x480
       __vfs_setxattr_noperm+0x12d/0x660
       vfs_setxattr+0x163/0x360
       filename_setxattr+0x296/0x630
       path_setxattrat+0x3eb/0x440
       __x64_sys_setxattr+0xbc/0xe0
       do_syscall_64+0x174/0x580
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&oi->ip_xattr_sem){++++}-{4:4}:
       __lock_acquire+0x15a5/0x2cf0
       lock_acquire+0x106/0x350
       down_read+0x47/0x2e0
       ocfs2_init_acl+0x2fd/0x7e0
       ocfs2_mknod+0x1679/0x2260
       ocfs2_create+0x195/0x460
       path_openat+0x1395/0x3860
       do_file_open+0x23e/0x4a0
       do_sys_openat2+0x113/0x200
       __x64_sys_openat+0x138/0x170
       do_syscall_64+0x174/0x580
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &oi->ip_xattr_sem --> sb_internal#6 --> &journal->j_trans_barrier

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(&journal->j_trans_barrier);
                               lock(sb_internal#6);
                               lock(&journal->j_trans_barrier);
  rlock(&oi->ip_xattr_sem);

 *** DEADLOCK ***

8 locks held by syz.2.4299/23047:
 #0: ffff888174852410 (sb_writers#21){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff8881bb7feba0 (&type->i_mutex_dir_key#15){++++}-{4:4}, at: path_openat+0xb4c/0x3860
 #2: ffff8881bb7179a0 (&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_reserve_suballoc_bits+0x16d/0x4840
 #3: ffff8881bb7141a0 (&ocfs2_sysfile_lock_key[EXTENT_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_reserve_suballoc_bits+0x16d/0x4840
 #4: ffff8881bb7125a0 (&ocfs2_sysfile_lock_key[LOCAL_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_reserve_local_alloc_bits+0x11f/0x2660
 #5: ffff888174852600 (sb_internal#6){.+.+}-{0:0}, at: ocfs2_mknod+0x1181/0x2260
 #6: ffff88816edc78e0 (&journal->j_trans_barrier){.+.+}-{4:4}, at: ocfs2_start_trans+0x3ab/0x700
 #7: ffff888174856938 (jbd2_handle#2){.+.+}-{0:0}, at: start_this_handle+0x2054/0x2290

stack backtrace:
CPU: 1 UID: 0 PID: 23047 Comm: syz.2.4299 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
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+0xe8/0x150
 print_circular_bug+0x2e1/0x300
 check_noncircular+0x12e/0x150
 __lock_acquire+0x15a5/0x2cf0
 lock_acquire+0x106/0x350
 down_read+0x47/0x2e0
 ocfs2_init_acl+0x2fd/0x7e0
 ocfs2_mknod+0x1679/0x2260
 ocfs2_create+0x195/0x460
 path_openat+0x1395/0x3860
 do_file_open+0x23e/0x4a0
 do_sys_openat2+0x113/0x200
 __x64_sys_openat+0x138/0x170
 do_syscall_64+0x174/0x580
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc044d9ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc045c66028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fc045015fa0 RCX: 00007fc044d9ce59
RDX: 000000000000275a RSI: 0000200000000200 RDI: ffffffffffffff9c
RBP: 00007fc044e32d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc045016038 R14: 00007fc045015fa0 R15: 00007ffd1eebf808
 </TASK>
