ocfs2: Slot 0 on device (7,4) was already allocated to this node!
ocfs2: Mounting device (7,4) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.4.315/8021 is trying to acquire lock:
ffff88811a0e26c0 (&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_evict_inode+0x153d/0x4100

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

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/0xfa0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&ocfs2_quota_ip_alloc_sem_key){++++}-{4:4}:
       lock_acquire+0x120/0x360
       down_write+0x96/0x1f0
       ocfs2_create_local_dquot+0x19d/0x1a40
       ocfs2_acquire_dquot+0x80f/0xb30
       dqget+0x7b1/0xf10
       __dquot_initialize+0x3b3/0xcb0
       ocfs2_get_init_inode+0x13b/0x1b0
       ocfs2_mknod+0x863/0x2050
       ocfs2_create+0x1a5/0x440
       path_openat+0x14f4/0x3830
       do_filp_open+0x1fa/0x410
       do_sys_openat2+0x121/0x1c0
       __x64_sys_openat+0x138/0x170
       do_syscall_64+0xfa/0xfa0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&dquot->dq_lock){+.+.}-{4:4}:
       lock_acquire+0x120/0x360
       __mutex_lock+0x187/0x1350
       dqget+0x72a/0xf10
       __dquot_initialize+0x3b3/0xcb0
       ocfs2_get_init_inode+0x13b/0x1b0
       ocfs2_mknod+0x863/0x2050
       ocfs2_create+0x1a5/0x440
       path_openat+0x14f4/0x3830
       do_filp_open+0x1fa/0x410
       do_sys_openat2+0x121/0x1c0
       __x64_sys_openat+0x138/0x170
       do_syscall_64+0xfa/0xfa0
       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/0x4100
       evict+0x504/0x9c0
       ocfs2_dentry_iput+0x247/0x370
       __dentry_kill+0x209/0x660
       dput+0x19f/0x2b0
       do_renameat2+0x6b2/0xa50
       __x64_sys_rename+0x82/0x90
       do_syscall_64+0xfa/0xfa0
       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] --> &ocfs2_quota_ip_alloc_sem_key --> &ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]);
                               lock(&ocfs2_quota_ip_alloc_sem_key);
                               lock(&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]);
  lock(&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]);

 *** DEADLOCK ***

4 locks held by syz.4.315/8021:
 #0: ffff88801c4a4420 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff88811a0e89c0 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: do_renameat2+0x3b9/0xa50
 #2: ffff888113798bd0 (&osb->nfs_sync_rwlock){.+.+}-{4:4}, at: ocfs2_nfs_sync_lock+0x106/0x250
 #3: ffff88811a0e1840 (&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_evict_inode+0xf86/0x4100

stack backtrace:
CPU: 0 UID: 0 PID: 8021 Comm: syz.4.315 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/0x4100
 evict+0x504/0x9c0
 ocfs2_dentry_iput+0x247/0x370
 __dentry_kill+0x209/0x660
 dput+0x19f/0x2b0
 do_renameat2+0x6b2/0xa50
 __x64_sys_rename+0x82/0x90
 do_syscall_64+0xfa/0xfa0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f84a818efc9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f84a90b3038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f84a83e5fa0 RCX: 00007f84a818efc9
RDX: 0000000000000000 RSI: 00002000000003c0 RDI: 0000200000000400
RBP: 00007f84a8211f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f84a83e6038 R14: 00007f84a83e5fa0 R15: 00007ffedcf39ee8
 </TASK>
