JBD2: Ignoring recovery information on journal ocfs2: Mounting device (7,1) on (node local, slot 0) with ordered data mode. ====================================================== WARNING: possible circular locking dependency detected 6.13.0-rc3-syzkaller-00073-geabcdba3ad40 #0 Not tainted ------------------------------------------------------ syz.1.3422/15926 is trying to acquire lock: ffff88805920a640 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#3){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:818 [inline] ffff88805920a640 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#3){+.+.}-{4:4}, at: ocfs2_xattr_set+0xd2e/0x2a30 fs/ocfs2/xattr.c:3622 but task is already holding lock: ffff88805920ce38 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_xattr_set+0x416/0x2a30 fs/ocfs2/xattr.c:3583 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&oi->ip_xattr_sem){++++}-{4:4}: down_read+0x9a/0x330 kernel/locking/rwsem.c:1524 ocfs2_init_acl+0x2fd/0x7d0 fs/ocfs2/acl.c:366 ocfs2_mknod+0xd0a/0x2440 fs/ocfs2/namei.c:410 ocfs2_create+0x185/0x450 fs/ocfs2/namei.c:674 lookup_open.isra.0+0x1177/0x14c0 fs/namei.c:3649 open_last_lookups fs/namei.c:3748 [inline] path_openat+0x904/0x2d60 fs/namei.c:3984 do_filp_open+0x20c/0x470 fs/namei.c:4014 do_sys_openat2+0x17a/0x1e0 fs/open.c:1402 do_sys_open fs/open.c:1417 [inline] __do_sys_openat fs/open.c:1433 [inline] __se_sys_openat fs/open.c:1428 [inline] __x64_sys_openat+0x175/0x210 fs/open.c:1428 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (jbd2_handle){++++}-{0:0}: jbd2_journal_lock_updates+0xa5/0x340 fs/jbd2/transaction.c:865 __ocfs2_flush_truncate_log+0x28e/0x1150 fs/ocfs2/alloc.c:6029 ocfs2_flush_truncate_log+0x4a/0x70 fs/ocfs2/alloc.c:6076 ocfs2_sync_fs+0x1c8/0x3d0 fs/ocfs2/super.c:402 sync_filesystem+0x1cf/0x290 fs/sync.c:66 generic_shutdown_super+0x7e/0x3d0 fs/super.c:621 kill_block_super+0x3b/0x90 fs/super.c:1710 deactivate_locked_super+0xc1/0x1a0 fs/super.c:473 deactivate_super+0xde/0x100 fs/super.c:506 cleanup_mnt+0x222/0x450 fs/namespace.c:1373 task_work_run+0x151/0x250 kernel/task_work.c:239 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop kernel/entry/common.c:114 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x27b/0x2a0 kernel/entry/common.c:218 do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#3){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x249e/0x3c40 kernel/locking/lockdep.c:5226 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5849 down_write+0x93/0x200 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:818 [inline] ocfs2_xattr_set+0xd2e/0x2a30 fs/ocfs2/xattr.c:3622 __vfs_setxattr+0x176/0x1e0 fs/xattr.c:200 __vfs_setxattr_noperm+0x127/0x660 fs/xattr.c:234 __vfs_setxattr_locked+0x182/0x260 fs/xattr.c:295 vfs_setxattr+0x146/0x360 fs/xattr.c:321 do_setxattr+0x142/0x170 fs/xattr.c:636 filename_setxattr+0x16d/0x1d0 fs/xattr.c:665 path_setxattrat+0x1e0/0x290 fs/xattr.c:713 __do_sys_setxattr fs/xattr.c:747 [inline] __se_sys_setxattr fs/xattr.c:743 [inline] __x64_sys_setxattr+0xc6/0x140 fs/xattr.c:743 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Chain exists of: &ocfs2_sysfile_lock_key[args->fi_sysfile_type]#3 --> jbd2_handle --> &oi->ip_xattr_sem Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&oi->ip_xattr_sem); lock(jbd2_handle); lock(&oi->ip_xattr_sem); lock(&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#3); *** DEADLOCK *** 3 locks held by syz.1.3422/15926: #0: ffff888032b2a420 (sb_writers#29){.+.+}-{0:0}, at: filename_setxattr+0xbc/0x1d0 fs/xattr.c:663 #1: ffff88805920d100 (&sb->s_type->i_mutex_key#35){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:818 [inline] #1: ffff88805920d100 (&sb->s_type->i_mutex_key#35){+.+.}-{4:4}, at: vfs_setxattr+0x123/0x360 fs/xattr.c:320 #2: ffff88805920ce38 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_xattr_set+0x416/0x2a30 fs/ocfs2/xattr.c:3583 stack backtrace: CPU: 0 UID: 0 PID: 15926 Comm: syz.1.3422 Not tainted 6.13.0-rc3-syzkaller-00073-geabcdba3ad40 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x419/0x5d0 kernel/locking/lockdep.c:2074 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x249e/0x3c40 kernel/locking/lockdep.c:5226 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5849 down_write+0x93/0x200 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:818 [inline] ocfs2_xattr_set+0xd2e/0x2a30 fs/ocfs2/xattr.c:3622 __vfs_setxattr+0x176/0x1e0 fs/xattr.c:200 __vfs_setxattr_noperm+0x127/0x660 fs/xattr.c:234 __vfs_setxattr_locked+0x182/0x260 fs/xattr.c:295 vfs_setxattr+0x146/0x360 fs/xattr.c:321 do_setxattr+0x142/0x170 fs/xattr.c:636 filename_setxattr+0x16d/0x1d0 fs/xattr.c:665 path_setxattrat+0x1e0/0x290 fs/xattr.c:713 __do_sys_setxattr fs/xattr.c:747 [inline] __se_sys_setxattr fs/xattr.c:743 [inline] __x64_sys_setxattr+0xc6/0x140 fs/xattr.c:743 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fd4b1b85d29 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:00007fd4af9f6038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc RAX: ffffffffffffffda RBX: 00007fd4b1d75fa0 RCX: 00007fd4b1b85d29 RDX: 0000000000000000 RSI: 0000000020000100 RDI: 0000000020000000 RBP: 00007fd4b1c01aa8 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fd4b1d75fa0 R15: 00007ffd9147f128 OCFS2: ERROR (device loop1): ocfs2_validate_gd_self: Group descriptor #32 has an invalid bg_blkno of 0 On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. OCFS2: File system is now read-only. (syz.1.3422,15926,1):ocfs2_search_chain:1814 ERROR: status = -30 (syz.1.3422,15926,0):ocfs2_search_chain:1926 ERROR: status = -30 (syz.1.3422,15926,0):ocfs2_claim_suballoc_bits:1995 ERROR: status = -30 (syz.1.3422,15926,0):ocfs2_claim_suballoc_bits:2038 ERROR: status = -30 (syz.1.3422,15926,0):__ocfs2_claim_clusters:2412 ERROR: status = -30 (syz.1.3422,15926,0):__ocfs2_claim_clusters:2420 ERROR: status = -30 (syz.1.3422,15926,0):ocfs2_block_group_alloc_contig:437 ERROR: status = -30 (syz.1.3422,15926,0):ocfs2_block_group_alloc:709 ERROR: status = -30 (syz.1.3422,15926,0):ocfs2_block_group_alloc:762 ERROR: status = -30 (syz.1.3422,15926,0):ocfs2_reserve_suballoc_bits:837 ERROR: status = -30 (syz.1.3422,15926,0):ocfs2_reserve_suballoc_bits:854 ERROR: status = -30 (syz.1.3422,15926,0):ocfs2_reserve_new_metadata_blocks:994 ERROR: status = -30 (syz.1.3422,15926,0):ocfs2_reserve_new_metadata_blocks:1017 ERROR: status = -30 (syz.1.3422,15926,0):ocfs2_init_xattr_set_ctxt:3280 ERROR: status = -30 (syz.1.3422,15926,0):ocfs2_xattr_set:3637 ERROR: status = -30 ocfs2: Unmounting device (7,1) on (node local)