======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz-executor/6048 is trying to acquire lock:
ffff88811f51dda0 (&ocfs2_sysfile_lock_key[GLOBAL_BITMAP_SYSTEM_INODE]){+.+.}-{4:4}, at: _ocfs2_free_suballoc_bits+0x1510/0x27a0

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

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&journal->j_trans_barrier){.+.+}-{4:4}:
       down_read+0x4a/0x330
       ocfs2_start_trans+0x3ae/0x700
       ocfs2_reserve_suballoc_bits+0x7b7/0x4850
       ocfs2_reserve_new_inode+0x4f8/0xd10
       ocfs2_mknod+0x894/0x22b0
       ocfs2_create+0x195/0x460
       lookup_open+0xc0d/0x1a40
       path_openat+0x677/0x1d60
       do_file_open+0x23e/0x4a0
       do_sys_openat2+0x115/0x200
       __x64_sys_openat+0x138/0x170
       do_syscall_64+0x166/0x520
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (sb_internal#3){.+.+}-{0:0}:
       ocfs2_start_trans+0x2ac/0x700
       ocfs2_reserve_suballoc_bits+0x7b7/0x4850
       ocfs2_reserve_new_inode+0x4f8/0xd10
       ocfs2_mknod+0x894/0x22b0
       ocfs2_create+0x195/0x460
       lookup_open+0xc0d/0x1a40
       path_openat+0x677/0x1d60
       do_file_open+0x23e/0x4a0
       do_sys_openat2+0x115/0x200
       __x64_sys_openat+0x138/0x170
       do_syscall_64+0x166/0x520
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ocfs2_sysfile_lock_key[GLOBAL_BITMAP_SYSTEM_INODE]){+.+.}-{4:4}:
       __lock_acquire+0x1520/0x2cf0
       lock_acquire+0x106/0x350
       down_write+0x96/0x200
       _ocfs2_free_suballoc_bits+0x1510/0x27a0
       ocfs2_free_dinode+0xb1/0xe0
       ocfs2_evict_inode+0x1dee/0x4390
       evict+0x624/0xb50
       vfs_rmdir+0x413/0x6a0
       filename_rmdir+0x292/0x520
       __se_sys_unlinkat+0x71/0x1a0
       do_syscall_64+0x166/0x520
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &ocfs2_sysfile_lock_key[GLOBAL_BITMAP_SYSTEM_INODE] --> 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);
  lock(&ocfs2_sysfile_lock_key[GLOBAL_BITMAP_SYSTEM_INODE]);

 *** DEADLOCK ***

locks held by syz-executor/6048: 8, last CPU#1:
 #0: ffff888119bca460 (sb_writers#20){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff8881204b25a0 (&type->i_mutex_dir_key#14/1){+.+.}-{4:4}, at: filename_rmdir+0x1cd/0x520
 #2: ffff888113c10bc0 (&osb->nfs_sync_rwlock){.+.+}-{4:4}, at: ocfs2_nfs_sync_lock+0x106/0x270
 #3: ffff88811f51cfa0 (&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_evict_inode+0xe39/0x4390
 #4: ffff88811f51b3a0 (&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_evict_inode+0x1489/0x4390
 #5: ffff888119bca650 (sb_internal#3){.+.+}-{0:0}, at: ocfs2_evict_inode+0x156b/0x4390
 #6: ffff8880286400e0 (&journal->j_trans_barrier){.+.+}-{4:4}, at: ocfs2_start_trans+0x3ae/0x700
 #7: ffff88810eb7e938 (jbd2_handle#2){.+.+}-{0:0}, at: start_this_handle+0x1fbf/0x2200

stack backtrace:
CPU: 1 UID: 0 PID: 6048 Comm: syz-executor 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+0x1520/0x2cf0
 lock_acquire+0x106/0x350
 down_write+0x96/0x200
 _ocfs2_free_suballoc_bits+0x1510/0x27a0
 ocfs2_free_dinode+0xb1/0xe0
 ocfs2_evict_inode+0x1dee/0x4390
 evict+0x624/0xb50
 vfs_rmdir+0x413/0x6a0
 filename_rmdir+0x292/0x520
 __se_sys_unlinkat+0x71/0x1a0
 do_syscall_64+0x166/0x520
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f5fe999d277
Code: 77 01 c3 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 b8 07 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:00007ffc52010b68 EFLAGS: 00000207 ORIG_RAX: 0000000000000107
RAX: ffffffffffffffda RBX: 0000000000000065 RCX: 00007f5fe999d277
RDX: 0000000000000200 RSI: 00007ffc52011d10 RDI: 00000000ffffff9c
RBP: 00007f5fe9a344bb R08: 0000000000008560 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000207 R12: 00007ffc52011d10
R13: 00007f5fe9a344bb R14: 0000000000014374 R15: 00007ffc52013ed0
 </TASK>
ocfs2: Unmounting device (7,5) on (node local)
EXT4-fs (loop5): unmounting filesystem 00000000-0000-0000-0000-000000000000.
EXT4-fs error (device loop5): __ext4_get_inode_loc:4916: comm syz-executor: Invalid inode table block 1 in block_group 0
loop5: lost filesystem error report for type 5 error -117
EXT4-fs error (device loop5) in ext4_reserve_inode_write:6517: Corrupt filesystem
loop5: lost filesystem error report for type 5 error -117
EXT4-fs error (device loop5): ext4_quota_off:7353: inode #3: comm syz-executor: mark_inode_dirty error
loop5: lost file I/O error report for ino 3 type 5 pos 0x0 len 0x0 error -117
EXT4-fs error (device loop5): __ext4_get_inode_loc:4916: comm syz-executor: Invalid inode table block 1 in block_group 0
loop5: lost filesystem error report for type 5 error -117
