====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.9.3463/21879 is trying to acquire lock: ffff888079f2c650 (sb_internal #5 ){.+.+}-{0:0} , at: ocfs2_setattr+0xbc2/0x1ad0 fs/ocfs2/file.c:1266 but task is already holding lock: ffff88805db95be0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_setattr+0xbb3/0x1ad0 fs/ocfs2/file.c:1265 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}: down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498 ocfs2_read_virt_blocks+0x237/0x8d0 fs/ocfs2/extent_map.c:984 ocfs2_read_dir_block+0xd1/0x4f0 fs/ocfs2/dir.c:508 ocfs2_dir_foreach_blk_el fs/ocfs2/dir.c:1842 [inline] ocfs2_dir_foreach_blk+0x264/0x19d0 fs/ocfs2/dir.c:1928 ocfs2_dir_foreach fs/ocfs2/dir.c:1938 [inline] ocfs2_empty_dir+0x1a8/0x730 fs/ocfs2/dir.c:2156 ocfs2_rename+0x21c0/0x3960 fs/ocfs2/namei.c:1499 vfs_rename+0xbe1/0x1100 fs/namei.c:4840 do_renameat2+0x8b7/0xf60 fs/namei.c:4993 __do_sys_rename fs/namei.c:5039 [inline] __se_sys_rename fs/namei.c:5037 [inline] __x64_sys_rename+0x82/0x90 fs/namei.c:5037 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #1 (&journal->j_trans_barrier){.+.+}-{3:3}: down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498 ocfs2_start_trans+0x3a6/0x6f0 fs/ocfs2/journal.c:374 ocfs2_shutdown_local_alloc+0x1f8/0xaa0 fs/ocfs2/localalloc.c:416 ocfs2_dismount_volume+0x1e1/0x8a0 fs/ocfs2/super.c:1885 generic_shutdown_super+0x130/0x300 fs/super.c:475 kill_block_super+0x7c/0xe0 fs/super.c:1427 deactivate_locked_super+0x93/0xf0 fs/super.c:335 cleanup_mnt+0x42d/0x4e0 fs/namespace.c:1148 task_work_run+0x125/0x1a0 kernel/task_work.c:188 tracehook_notify_resume include/linux/tracehook.h:189 [inline] exit_to_user_mode_loop+0x10f/0x130 kernel/entry/common.c:181 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214 __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline] syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #0 (sb_internal#5){.+.+}-{0:0}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c42/0x7d10 kernel/locking/lockdep.c:5012 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1811 [inline] sb_start_intwrite include/linux/fs.h:1928 [inline] ocfs2_start_trans+0x2a7/0x6f0 fs/ocfs2/journal.c:372 ocfs2_setattr+0xbc2/0x1ad0 fs/ocfs2/file.c:1266 notify_change+0xbcd/0xee0 fs/attr.c:505 ovl_workdir_create+0x446/0x630 fs/overlayfs/super.c:830 ovl_make_workdir fs/overlayfs/super.c:1376 [inline] ovl_get_workdir+0x37c/0x1230 fs/overlayfs/super.c:1526 ovl_fill_super+0x1824/0x2a30 fs/overlayfs/super.c:2082 mount_nodev+0x52/0xe0 fs/super.c:1446 legacy_get_tree+0xe6/0x180 fs/fs_context.c:611 vfs_get_tree+0x88/0x270 fs/super.c:1530 do_new_mount+0x24a/0xa40 fs/namespace.c:3034 do_mount fs/namespace.c:3377 [inline] __do_sys_mount fs/namespace.c:3585 [inline] __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 other info that might help us debug this: Chain exists of: sb_internal#5 --> &journal->j_trans_barrier --> &ocfs2_file_ip_alloc_sem_key Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ocfs2_file_ip_alloc_sem_key); lock(&journal->j_trans_barrier); lock(&ocfs2_file_ip_alloc_sem_key); lock(sb_internal#5); *** DEADLOCK *** 5 locks held by syz.9.3463/21879: #0: ffff88808a19e0e0 (&type->s_umount_key#66/1){+.+.}-{3:3}, at: alloc_super+0x201/0x950 fs/super.c:229 #1: ffff888079f2c460 (sb_writers#37){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:386 #2: ffff88805db95108 (&sb->s_type->i_mutex_key#46/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline] #2: ffff88805db95108 (&sb->s_type->i_mutex_key#46/1){+.+.}-{3:3}, at: ovl_workdir_create+0x140/0x630 fs/overlayfs/super.c:768 #3: ffff88805db95f48 (&sb->s_type->i_mutex_key#47){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline] #3: ffff88805db95f48 (&sb->s_type->i_mutex_key#47){+.+.}-{3:3}, at: ovl_workdir_create+0x42b/0x630 fs/overlayfs/super.c:829 #4: ffff88805db95be0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_setattr+0xbb3/0x1ad0 fs/ocfs2/file.c:1265 stack backtrace: CPU: 1 PID: 21879 Comm: syz.9.3463 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 Call Trace: dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2133 check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c42/0x7d10 kernel/locking/lockdep.c:5012 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1811 [inline] sb_start_intwrite include/linux/fs.h:1928 [inline] ocfs2_start_trans+0x2a7/0x6f0 fs/ocfs2/journal.c:372 ocfs2_setattr+0xbc2/0x1ad0 fs/ocfs2/file.c:1266 notify_change+0xbcd/0xee0 fs/attr.c:505 ovl_workdir_create+0x446/0x630 fs/overlayfs/super.c:830 ovl_make_workdir fs/overlayfs/super.c:1376 [inline] ovl_get_workdir+0x37c/0x1230 fs/overlayfs/super.c:1526 ovl_fill_super+0x1824/0x2a30 fs/overlayfs/super.c:2082 mount_nodev+0x52/0xe0 fs/super.c:1446 legacy_get_tree+0xe6/0x180 fs/fs_context.c:611 vfs_get_tree+0x88/0x270 fs/super.c:1530 do_new_mount+0x24a/0xa40 fs/namespace.c:3034 do_mount fs/namespace.c:3377 [inline] __do_sys_mount fs/namespace.c:3585 [inline] __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 RIP: 0033:0x7f12b6498e59 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:00007f12b46f2028 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00007f12b6711fa0 RCX: 00007f12b6498e59 RDX: 0000200000000000 RSI: 0000200000000340 RDI: 0000000000000000 RBP: 00007f12b652ed6f R08: 00002000000000c0 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f12b6712038 R14: 00007f12b6711fa0 R15: 00007ffee59d25c8 overlayfs: upper fs does not support tmpfile. overlayfs: upper fs does not support RENAME_WHITEOUT. OCFS2: ERROR (device loop9): int ocfs2_validate_gd_self(struct super_block *, struct buffer_head *, int): Group descriptor #20 has bad signature On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. OCFS2: File system is now read-only. (syz.9.3463,21879,1):ocfs2_search_chain:1761 ERROR: status = -30 (syz.9.3463,21879,1):ocfs2_search_chain:1871 ERROR: status = -30 (syz.9.3463,21879,1):ocfs2_claim_suballoc_bits:1950 ERROR: status = -30 (syz.9.3463,21879,1):ocfs2_claim_suballoc_bits:1993 ERROR: status = -30 (syz.9.3463,21879,1):ocfs2_claim_metadata:2018 ERROR: status = -30 (syz.9.3463,21879,1):ocfs2_claim_metadata:2031 ERROR: status = -30 (syz.9.3463,21879,1):ocfs2_create_xattr_block:2891 ERROR: status = -30 (syz.9.3463,21879,1):ocfs2_xattr_block_set:2972 ERROR: status = -30 overlayfs: failed to set xattr on upper overlayfs: ...falling back to index=off,metacopy=off. overlayfs: upper fs missing required features. ocfs2: Unmounting device (7,9) on (node local)