JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,2) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.2.5377/28796 is trying to acquire lock:
ffff888011b4b540 (&ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_xattr_set+0xba7/0x13e0

but task is already holding lock:
ffff888011b486f8 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_xattr_set+0x475/0x13e0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&oi->ip_xattr_sem){++++}-{4:4}:
       down_read+0x47/0x2e0
       ocfs2_init_acl+0x2fd/0x7e0
       ocfs2_mknod+0x1423/0x2210
       ocfs2_mkdir+0x181/0x430
       vfs_mkdir+0x511/0x5b0
       do_mkdirat+0x27d/0x4b0
       __x64_sys_mkdirat+0x87/0xa0
       do_syscall_64+0xe2/0xf80
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&journal->j_trans_barrier){.+.+}-{4:4}:
       down_read+0x47/0x2e0
       ocfs2_start_trans+0x3ab/0x700
       ocfs2_mknod+0xf31/0x2210
       ocfs2_create+0x195/0x440
       path_openat+0x18dd/0x3e20
       do_filp_open+0x22d/0x490
       do_sys_openat2+0x12f/0x220
       __x64_sys_openat+0x138/0x170
       do_syscall_64+0xe2/0xf80
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (sb_internal#2){.+.+}-{0:0}:
       ocfs2_start_trans+0x2ac/0x700
       ocfs2_remove_btree_range+0x84c/0x1610
       ocfs2_commit_truncate+0xbb8/0x22f0
       ocfs2_evict_inode+0x1023/0x42e0
       evict+0x61e/0xb10
       do_unlinkat+0x354/0x590
       __x64_sys_unlink+0x47/0x50
       do_syscall_64+0xe2/0xf80
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE]){+.+.}-{4:4}:
       __lock_acquire+0x15a5/0x2cf0
       lock_acquire+0x106/0x330
       down_write+0x96/0x200
       ocfs2_xattr_set+0xba7/0x13e0
       __vfs_setxattr+0x43c/0x480
       __vfs_setxattr_noperm+0x12d/0x660
       vfs_setxattr+0x16a/0x2e0
       filename_setxattr+0x281/0x630
       path_setxattrat+0x3f3/0x430
       __x64_sys_setxattr+0xbc/0xe0
       do_syscall_64+0xe2/0xf80
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

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

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&oi->ip_xattr_sem);
                               lock(&journal->j_trans_barrier);
                               lock(&oi->ip_xattr_sem);
  lock(&ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE]);

 *** DEADLOCK ***

3 locks held by syz.2.5377/28796:
 #0: ffff8881114c4420 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff888011b489c0 (&sb->s_type->i_mutex_key#27){++++}-{4:4}, at: vfs_setxattr+0x143/0x2e0
 #2: ffff888011b486f8 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_xattr_set+0x475/0x13e0

stack backtrace:
CPU: 0 UID: 0 PID: 28796 Comm: syz.2.5377 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
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/0x330
 down_write+0x96/0x200
 ocfs2_xattr_set+0xba7/0x13e0
 __vfs_setxattr+0x43c/0x480
 __vfs_setxattr_noperm+0x12d/0x660
 vfs_setxattr+0x16a/0x2e0
 filename_setxattr+0x281/0x630
 path_setxattrat+0x3f3/0x430
 __x64_sys_setxattr+0xbc/0xe0
 do_syscall_64+0xe2/0xf80
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fcc1fd9acb9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fcc20b93028 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007fcc20015fa0 RCX: 00007fcc1fd9acb9
RDX: 0000000000000000 RSI: 00002000000003c0 RDI: 0000200000000380
RBP: 00007fcc1fe08bf7 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fcc20016038 R14: 00007fcc20015fa0 R15: 00007fff822a5978
 </TASK>
OCFS2: ERROR (device loop2): int ocfs2_validate_gd_parent(struct super_block *, struct ocfs2_dinode *, struct buffer_head *, int): Group descriptor #32 has bit count of 1024
On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted.
OCFS2: File system is now read-only.
(syz.2.5377,28796,0):ocfs2_search_chain:1818 ERROR: status = -30
(syz.2.5377,28796,0):ocfs2_search_chain:1941 ERROR: status = -30
(syz.2.5377,28796,0):ocfs2_claim_suballoc_bits:2021 ERROR: status = -30
(syz.2.5377,28796,0):ocfs2_claim_suballoc_bits:2074 ERROR: status = -30
(syz.2.5377,28796,0):__ocfs2_claim_clusters:2449 ERROR: status = -30
(syz.2.5377,28796,0):__ocfs2_claim_clusters:2457 ERROR: status = -30
(syz.2.5377,28796,0):ocfs2_block_group_alloc_contig:438 ERROR: status = -30
(syz.2.5377,28796,0):ocfs2_block_group_alloc:712 ERROR: status = -30
(syz.2.5377,28796,0):ocfs2_block_group_alloc:765 ERROR: status = -30
(syz.2.5377,28796,0):ocfs2_reserve_suballoc_bits:840 ERROR: status = -30
(syz.2.5377,28796,0):ocfs2_reserve_suballoc_bits:857 ERROR: status = -30
(syz.2.5377,28796,0):ocfs2_reserve_new_metadata_blocks:997 ERROR: status = -30
(syz.2.5377,28796,0):ocfs2_reserve_new_metadata_blocks:1020 ERROR: status = -30
(syz.2.5377,28796,0):ocfs2_init_xattr_set_ctxt:3310 ERROR: status = -30
(syz.2.5377,28796,0):ocfs2_xattr_set:3667 ERROR: status = -30
