======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz-executor/7562 is trying to acquire lock:
ffff888116d309c0 (&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_evict_inode+0x153d/0x40e0

but task is already holding lock:
ffff88812d8460c0 (&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_evict_inode+0xf86/0x40e0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]){+.+.}-{4:4}:
       lock_acquire+0x120/0x360
       down_write+0x96/0x1f0
       ocfs2_del_inode_from_orphan+0x134/0x740
       ocfs2_dio_end_io+0x479/0x10f0
       dio_complete+0x25b/0x790
       __blockdev_direct_IO+0x2e63/0x3490
       ocfs2_direct_IO+0x25f/0x2d0
       generic_file_direct_write+0x1db/0x3e0
       __generic_file_write_iter+0x11d/0x230
       ocfs2_file_write_iter+0x157a/0x1d10
       iter_file_splice_write+0x975/0x10e0
       direct_splice_actor+0x101/0x160
       splice_direct_to_actor+0x5a8/0xcc0
       do_splice_direct+0x181/0x270
       do_sendfile+0x4da/0x7e0
       __se_sys_sendfile64+0x13e/0x190
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&oi->ip_alloc_sem){++++}-{4:4}:
       lock_acquire+0x120/0x360
       down_write+0x96/0x1f0
       ocfs2_try_remove_refcount_tree+0xb6/0x320
       ocfs2_truncate_file+0xda0/0x1420
       ocfs2_setattr+0x1520/0x1b40
       notify_change+0xb36/0xe40
       do_truncate+0x1a4/0x220
       path_openat+0x306c/0x3830
       do_filp_open+0x1fa/0x410
       do_sys_openat2+0x121/0x1c0
       __x64_sys_creat+0x8f/0xc0
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&oi->ip_xattr_sem){++++}-{4:4}:
       lock_acquire+0x120/0x360
       down_read+0x46/0x2e0
       ocfs2_calc_xattr_init+0x20a/0xd80
       ocfs2_mknod+0xc92/0x2050
       ocfs2_mkdir+0x191/0x440
       vfs_mkdir+0x306/0x510
       do_mkdirat+0x247/0x590
       __x64_sys_mkdir+0x6c/0x80
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}:
       validate_chain+0xb9b/0x2140
       __lock_acquire+0xab9/0xd20
       lock_acquire+0x120/0x360
       down_write+0x96/0x1f0
       ocfs2_evict_inode+0x153d/0x40e0
       evict+0x504/0x9c0
       vfs_rmdir+0x3ec/0x520
       do_rmdir+0x25f/0x550
       __x64_sys_unlinkat+0xc2/0xf0
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE] --> &oi->ip_alloc_sem --> &ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]);
                               lock(&oi->ip_alloc_sem);
                               lock(&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]);
  lock(&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]);

 *** DEADLOCK ***

4 locks held by syz-executor/7562:
 #0: ffff888020ea2428 (sb_writers#15){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff88812d8409c0 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: do_rmdir+0x1b2/0x550
 #2: ffff888129784bd0 (&osb->nfs_sync_rwlock){++++}-{4:4}, at: ocfs2_nfs_sync_lock+0x106/0x250
 #3: ffff88812d8460c0 (&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_evict_inode+0xf86/0x40e0

stack backtrace:
CPU: 0 UID: 0 PID: 7562 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+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_evict_inode+0x153d/0x40e0
 evict+0x504/0x9c0
 vfs_rmdir+0x3ec/0x520
 do_rmdir+0x25f/0x550
 __x64_sys_unlinkat+0xc2/0xf0
 do_syscall_64+0xfa/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd7ccd8e1c7
Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 07 01 00 00 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:00007ffe716694e8 EFLAGS: 00000207 ORIG_RAX: 0000000000000107
RAX: ffffffffffffffda RBX: 0000000000000065 RCX: 00007fd7ccd8e1c7
RDX: 0000000000000200 RSI: 00007ffe7166a690 RDI: 00000000ffffff9c
RBP: 00007fd7cce11c05 R08: 000055557522866b R09: 0000000000000000
R10: 0000000000001000 R11: 0000000000000207 R12: 00007ffe7166a690
R13: 00007fd7cce11c05 R14: 00000000000313c0 R15: 00007ffe7166c850
 </TASK>
OCFS2: ERROR (device loop5): int ocfs2_validate_gd_parent(struct super_block *, struct ocfs2_dinode *, struct buffer_head *, int): Group descriptor #17056 has bad chain 7
On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted.
OCFS2: File system is now read-only.
(syz-executor,7562,0):_ocfs2_free_suballoc_bits:2579 ERROR: status = -30
(syz-executor,7562,0):ocfs2_remove_inode:775 ERROR: status = -30
(syz-executor,7562,0):ocfs2_wipe_inode:897 ERROR: status = -30
(syz-executor,7562,0):ocfs2_delete_inode:1158 ERROR: status = -30
ocfs2: Unmounting device (7,5) on (node local)
EXT4-fs (loop5): unmounting filesystem 00000000-0000-0000-0000-000000000000.
