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

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

-> #3 (&journal->j_trans_barrier){.+.+}-{4:4}:
       down_read+0x4a/0x330
       ocfs2_start_trans+0x3ab/0x700
       ocfs2_modify_bh+0xe3/0x4d0
       ocfs2_local_read_info+0x146b/0x1830
       dquot_load_quota_sb+0x76f/0xb70
       dquot_load_quota_inode+0x2dc/0x5d0
       ocfs2_enable_quotas+0x1c3/0x4a0
       ocfs2_fill_super+0x530c/0x6840
       get_tree_bdev_flags+0x430/0x4f0
       vfs_get_tree+0x92/0x2a0
       do_new_mount+0x319/0xdc0
       __se_sys_mount+0x31d/0x420
       do_syscall_64+0x174/0x580
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (sb_internal#3){.+.+}-{0:0}:
       lock_release+0x1a3/0x3c0
       up_write+0x2d/0x4a0
       ocfs2_free_alloc_context+0x97/0x1a0
       ocfs2_write_begin_nolock+0x4164/0x41f0
       ocfs2_write_begin+0x1ba/0x310
       generic_perform_write+0x2d5/0x8f0
       ocfs2_file_write_iter+0x1706/0x1f10
       vfs_write+0x612/0xba0
       ksys_write+0x150/0x270
       do_syscall_64+0x174/0x580
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&oi->ip_alloc_sem){++++}-{4:4}:
       down_write+0x96/0x200
       ocfs2_try_remove_refcount_tree+0xb6/0x360
       ocfs2_truncate_file+0xe90/0x14b0
       ocfs2_setattr+0x1641/0x1d10
       notify_change+0xbba/0xea0
       do_truncate+0x1c2/0x250
       path_openat+0x2fed/0x3830
       do_file_open+0x23e/0x4a0
       do_sys_openat2+0x115/0x200
       __x64_sys_open+0x11e/0x150
       do_syscall_64+0x174/0x580
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&oi->ip_xattr_sem){++++}-{4:4}:
       __lock_acquire+0x15ff/0x2e50
       lock_acquire+0x115/0x350
       down_read+0x4a/0x330
       ocfs2_init_acl+0x2fd/0x7e0
       ocfs2_mknod+0x166a/0x2240
       ocfs2_create+0x195/0x460
       vfs_create+0x2c4/0x450
       filename_mknodat+0x3e8/0x660
       __se_sys_mknod+0x3a/0x150
       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#3 --> &journal->j_trans_barrier

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

8 locks held by syz.3.980/9449:
 #0: ffff88811d9aa450 (sb_writers#28){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff88811d0697a0 (&type->i_mutex_dir_key#19/1){+.+.}-{4:4}, at: filename_create+0x200/0x370
 #2: ffff88811d0709a0 (&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_reserve_suballoc_bits+0x170/0x4850
 #3: ffff88811d0789a0 (&ocfs2_sysfile_lock_key[EXTENT_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_reserve_suballoc_bits+0x170/0x4850
 #4: ffff88811d0725a0 (&ocfs2_sysfile_lock_key[LOCAL_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_reserve_local_alloc_bits+0x11f/0x2680
 #5: ffff88811d9aa640 (sb_internal#3){.+.+}-{0:0}, at: ocfs2_mknod+0x116a/0x2240
 #6: ffff888115be1ce0 (&journal->j_trans_barrier){.+.+}-{4:4}, at: ocfs2_start_trans+0x3ab/0x700
 #7: ffff88811f77c938 (jbd2_handle#2){.+.+}-{0:0}, at: start_this_handle+0x1fc3/0x2210

stack backtrace:
CPU: 0 UID: 0 PID: 9449 Comm: syz.3.980 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+0xe8/0x150
 print_circular_bug+0x2e2/0x300
 check_noncircular+0x12f/0x150
 __lock_acquire+0x15ff/0x2e50
 lock_acquire+0x115/0x350
 down_read+0x4a/0x330
 ocfs2_init_acl+0x2fd/0x7e0
 ocfs2_mknod+0x166a/0x2240
 ocfs2_create+0x195/0x460
 vfs_create+0x2c4/0x450
 filename_mknodat+0x3e8/0x660
 __se_sys_mknod+0x3a/0x150
 do_syscall_64+0x174/0x580
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f197579e0d9
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:00007f197674b028 EFLAGS: 00000246 ORIG_RAX: 0000000000000085
RAX: ffffffffffffffda RBX: 00007f1975a25fa0 RCX: 00007f197579e0d9
RDX: 0000000000000707 RSI: 0000000000000000 RDI: 0000200000000000
RBP: 00007f1975835024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f1975a26038 R14: 00007f1975a25fa0 R15: 00007fff0e143d58
 </TASK>
(syz.3.980,9449,0):ocfs2_dio_end_io:2420 ERROR: Direct IO failed, bytes = -28
