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

but task is already holding lock:
ffff888174dbece0 (&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+0x47/0x2e0
       ocfs2_start_trans+0x3ab/0x700
       ocfs2_mknod+0x1181/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+0x15f/0xf80
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (sb_internal#5){.+.+}-{0:0}:
       lock_release+0x199/0x3c0
       up_write+0x2d/0x410
       ocfs2_free_alloc_context+0x97/0x1a0
       ocfs2_write_begin_nolock+0x410f/0x41a0
       ocfs2_dio_wr_get_block+0xbbf/0x1800
       __blockdev_direct_IO+0x161d/0x34e0
       ocfs2_direct_IO+0x251/0x2c0
       generic_file_direct_write+0x1db/0x3e0
       __generic_file_write_iter+0x11d/0x230
       ocfs2_file_write_iter+0x1663/0x1e70
       iter_file_splice_write+0x9a1/0x10f0
       direct_splice_actor+0x101/0x160
       splice_direct_to_actor+0x53a/0xc70
       do_splice_direct+0x195/0x290
       do_sendfile+0x535/0x7d0
       __se_sys_sendfile64+0x144/0x1a0
       do_syscall_64+0x15f/0xf80
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&oi->ip_alloc_sem){++++}-{4:4}:
       down_write+0x96/0x200
       ocfs2_try_remove_refcount_tree+0xb6/0x340
       ocfs2_truncate_file+0xdf3/0x14e0
       ocfs2_setattr+0x15e5/0x1ca0
       notify_change+0xc1a/0xf40
       do_truncate+0x1c2/0x250
       path_openat+0x2f89/0x3860
       do_file_open+0x23e/0x4a0
       do_sys_openat2+0x113/0x200
       __x64_sys_openat+0x138/0x170
       do_syscall_64+0x15f/0xf80
       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_mkdir+0x181/0x460
       vfs_mkdir+0x413/0x630
       filename_mkdirat+0x285/0x510
       __se_sys_mkdirat+0x35/0x150
       do_syscall_64+0x15f/0xf80
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

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

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

8 locks held by syz.8.420/8894:
 #0: ffff8881105a8410 (sb_writers#23){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff8881bb70cfa0 (&type->i_mutex_dir_key#14/1){+.+.}-{4:4}, at: filename_create+0x200/0x370
 #2: ffff8881bb4dcfa0 (&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_reserve_suballoc_bits+0x16d/0x4840
 #3: ffff8881bb7117a0 (&ocfs2_sysfile_lock_key[EXTENT_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_reserve_suballoc_bits+0x16d/0x4840
 #4: ffff88811fc4a5a0 (&ocfs2_sysfile_lock_key[LOCAL_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_reserve_local_alloc_bits+0x11f/0x2660
 #5: ffff8881105a8600 (sb_internal#5){.+.+}-{0:0}, at: ocfs2_mknod+0x1181/0x2260
 #6: ffff888174dbece0 (&journal->j_trans_barrier){.+.+}-{4:4}, at: ocfs2_start_trans+0x3ab/0x700
 #7: ffff88810f66a938 (jbd2_handle#2){.+.+}-{0:0}, at: start_this_handle+0x2054/0x2290

stack backtrace:
CPU: 0 UID: 0 PID: 8894 Comm: syz.8.420 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+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_mkdir+0x181/0x460
 vfs_mkdir+0x413/0x630
 filename_mkdirat+0x285/0x510
 __se_sys_mkdirat+0x35/0x150
 do_syscall_64+0x15f/0xf80
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f5de159bc47
Code: 00 66 90 48 89 f2 b9 00 01 00 00 48 89 fe bf 9c ff ff ff e9 db f7 ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 b8 02 01 00 00 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:00007f5de236de58 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f5de236dee0 RCX: 00007f5de159bc47
RDX: 00000000000001ff RSI: 0000200000000680 RDI: 00000000ffffff9c
RBP: 0000200000000080 R08: 0000200000000d40 R09: 0000000000000000
R10: 0000200000000080 R11: 0000000000000246 R12: 0000200000000680
R13: 00007f5de236dea0 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
(syz.8.420,8894,0):ocfs2_check_set_options:1244 ERROR: Invalid heartbeat mount options
