======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.6.214/7221 is trying to acquire lock:
ffff888167c69578 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_init_acl+0x2f9/0x720

but task is already holding lock:
ffff8881adae4950 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x1f87/0x21c0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (jbd2_handle){++++}-{0:0}:
       lock_acquire+0x120/0x360
       jbd2_journal_lock_updates+0xaa/0x360
       __ocfs2_flush_truncate_log+0x2ba/0x10e0
       ocfs2_flush_truncate_log+0x4f/0x70
       ocfs2_sync_fs+0x116/0x310
       sync_filesystem+0x1cf/0x230
       generic_shutdown_super+0x6f/0x2c0
       kill_block_super+0x44/0x90
       deactivate_locked_super+0xbc/0x130
       cleanup_mnt+0x425/0x4c0
       task_work_run+0x1d4/0x260
       exit_to_user_mode_loop+0xe9/0x130
       do_syscall_64+0x2bd/0xfa0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE]){+.+.}-{4:4}:
       lock_acquire+0x120/0x360
       down_write+0x96/0x1f0
       ocfs2_remove_btree_range+0x646/0x1540
       ocfs2_commit_truncate+0xb64/0x21d0
       ocfs2_truncate_file+0xca2/0x1420
       ocfs2_setattr+0x1520/0x1b40
       notify_change+0xc1a/0xf40
       do_truncate+0x1a4/0x220
       path_openat+0x306c/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 (&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+0xc1a/0xf40
       do_truncate+0x1a4/0x220
       path_openat+0x306c/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 (&oi->ip_xattr_sem){++++}-{4:4}:
       validate_chain+0xb9b/0x2140
       __lock_acquire+0xab9/0xd20
       lock_acquire+0x120/0x360
       down_read+0x46/0x2e0
       ocfs2_init_acl+0x2f9/0x720
       ocfs2_mknod+0x1321/0x2050
       ocfs2_mkdir+0x191/0x440
       vfs_mkdir+0x306/0x510
       do_mkdirat+0x247/0x590
       __x64_sys_mkdirat+0x87/0xa0
       do_syscall_64+0xfa/0xfa0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &oi->ip_xattr_sem --> &ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE] --> jbd2_handle

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(jbd2_handle);
                               lock(&ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE]);
                               lock(jbd2_handle);
  rlock(&oi->ip_xattr_sem);

 *** DEADLOCK ***

8 locks held by syz.6.214/7221:
 #0: ffff8881b8138420 (sb_writers#20){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff888167c69840 (&type->i_mutex_dir_key#12/1){+.+.}-{4:4}, at: filename_create+0x1f8/0x3c0
 #2: ffff88816cc509c0 (&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_reserve_suballoc_bits+0x15e/0x4640
 #3: ffff88816cc543c0 (&ocfs2_sysfile_lock_key[EXTENT_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_reserve_suballoc_bits+0x15e/0x4640
 #4: ffff88816cc560c0 (&ocfs2_sysfile_lock_key[GLOBAL_BITMAP_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_reserve_suballoc_bits+0x15e/0x4640
 #5: ffff8881b8138610 (sb_internal#5){.+.+}-{0:0}, at: ocfs2_mknod+0xe93/0x2050
 #6: ffff888111f95ce8 (&journal->j_trans_barrier){.+.+}-{4:4}, at: ocfs2_start_trans+0x36a/0x6d0
 #7: ffff8881adae4950 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x1f87/0x21c0

stack backtrace:
CPU: 0 UID: 0 PID: 7221 Comm: syz.6.214 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_read+0x46/0x2e0
 ocfs2_init_acl+0x2f9/0x720
 ocfs2_mknod+0x1321/0x2050
 ocfs2_mkdir+0x191/0x440
 vfs_mkdir+0x306/0x510
 do_mkdirat+0x247/0x590
 __x64_sys_mkdirat+0x87/0xa0
 do_syscall_64+0xfa/0xfa0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f950698d617
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 02 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:00007f95077b2e68 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f95077b2ef0 RCX: 00007f950698d617
RDX: 00000000000001ff RSI: 0000200000000680 RDI: 00000000ffffff9c
RBP: 0000200000000080 R08: 0000200000000140 R09: 0000000000000000
R10: 0000200000000080 R11: 0000000000000246 R12: 0000200000000680
R13: 00007f95077b2eb0 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
OCFS2: ERROR (device loop6): int ocfs2_mark_extent_written(struct inode *, struct ocfs2_extent_tree *, handle_t *, u32, u32, u32, struct ocfs2_alloc_context *, struct ocfs2_cached_dealloc_ctxt *): Inode 17059 has unwritten extents that are being written to, but the feature bit is not set in the super block
On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted.
OCFS2: File system is now read-only.
(syz.6.214,7221,1):ocfs2_dio_end_io_write:2355 ERROR: status = -30
overlay: ./file1\ is not a directory
