overlayfs: upper fs does not support tmpfile. overlayfs: upper fs does not support RENAME_WHITEOUT. overlayfs: upper fs missing required features. ====================================================== WARNING: possible circular locking dependency detected 5.15.185-syzkaller #0 Not tainted ------------------------------------------------------ syz.3.68/4421 is trying to acquire lock: ffff0000d7531488 (&osb->system_file_mutex){+.+.}-{3:3}, at: ocfs2_get_system_file_inode+0x15c/0x5ec fs/ocfs2/sysfile.c:101 but task is already holding lock: ffff0000ea003120 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_expand_inline_dir fs/ocfs2/dir.c:2819 [inline] ffff0000ea003120 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_extend_dir+0x498/0x390c fs/ocfs2/dir.c:3200 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}: down_read+0xc0/0x390 kernel/locking/rwsem.c:1498 ocfs2_read_virt_blocks+0x228/0x858 fs/ocfs2/extent_map.c:976 ocfs2_read_dir_block fs/ocfs2/dir.c:508 [inline] ocfs2_find_entry_el fs/ocfs2/dir.c:715 [inline] ocfs2_find_entry+0x314/0x1b84 fs/ocfs2/dir.c:1091 ocfs2_find_files_on_disk+0x10c/0x388 fs/ocfs2/dir.c:1995 ocfs2_lookup_ino_from_name+0x60/0x114 fs/ocfs2/dir.c:2017 _ocfs2_get_system_file_inode fs/ocfs2/sysfile.c:136 [inline] ocfs2_get_system_file_inode+0x288/0x5ec fs/ocfs2/sysfile.c:112 ocfs2_init_global_system_inodes+0x2a8/0x594 fs/ocfs2/super.c:458 ocfs2_initialize_super fs/ocfs2/super.c:2279 [inline] ocfs2_fill_super+0x3128/0x4074 fs/ocfs2/super.c:995 mount_bdev+0x264/0x358 fs/super.c:1400 ocfs2_mount+0x44/0x58 fs/ocfs2/super.c:1187 legacy_get_tree+0xd4/0x16c fs/fs_context.c:611 vfs_get_tree+0x90/0x274 fs/super.c:1530 do_new_mount+0x228/0x810 fs/namespace.c:3010 path_mount+0x5b4/0x1000 fs/namespace.c:3340 do_mount fs/namespace.c:3353 [inline] __do_sys_mount fs/namespace.c:3561 [inline] __se_sys_mount fs/namespace.c:3538 [inline] __arm64_sys_mount+0x514/0x5e4 fs/namespace.c:3538 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 -> #0 (&osb->system_file_mutex){+.+.}-{3:3}: 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+0x2928/0x651c kernel/locking/lockdep.c:5012 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x194/0x1edc kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0xac/0x11c kernel/locking/mutex.c:743 ocfs2_get_system_file_inode+0x15c/0x5ec fs/ocfs2/sysfile.c:101 ocfs2_reserve_suballoc_bits+0x11c/0x3a68 fs/ocfs2/suballoc.c:776 ocfs2_reserve_new_metadata_blocks+0x34c/0x7d8 fs/ocfs2/suballoc.c:978 ocfs2_expand_inline_dir fs/ocfs2/dir.c:2838 [inline] ocfs2_extend_dir+0x96c/0x390c fs/ocfs2/dir.c:3200 ocfs2_prepare_dir_for_insert+0x25c0/0x4408 fs/ocfs2/dir.c:4321 ocfs2_rename+0x140c/0x2e98 fs/ocfs2/namei.c:1478 vfs_rename+0x954/0xdcc fs/namei.c:4832 do_renameat2+0x74c/0xcdc fs/namei.c:4985 __do_sys_renameat2 fs/namei.c:5018 [inline] __se_sys_renameat2 fs/namei.c:5015 [inline] __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5015 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ocfs2_file_ip_alloc_sem_key); lock(&osb->system_file_mutex); lock(&ocfs2_file_ip_alloc_sem_key); lock(&osb->system_file_mutex); *** DEADLOCK *** 3 locks held by syz.3.68/4421: #0: ffff0000dd192460 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377 #1: ffff0000ea003488 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline] #1: ffff0000ea003488 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_renameat2+0x3bc/0xcdc fs/namei.c:4924 #2: ffff0000ea003120 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_expand_inline_dir fs/ocfs2/dir.c:2819 [inline] #2: ffff0000ea003120 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_extend_dir+0x498/0x390c fs/ocfs2/dir.c:3200 stack backtrace: CPU: 1 PID: 4421 Comm: syz.3.68 Not tainted 5.15.185-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call trace: dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216 __dump_stack+0x30/0x40 lib/dump_stack.c:88 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106 dump_stack+0x1c/0x5c lib/dump_stack.c:113 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2011 check_noncircular+0x240/0x2d4 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+0x2928/0x651c kernel/locking/lockdep.c:5012 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x194/0x1edc kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0xac/0x11c kernel/locking/mutex.c:743 ocfs2_get_system_file_inode+0x15c/0x5ec fs/ocfs2/sysfile.c:101 ocfs2_reserve_suballoc_bits+0x11c/0x3a68 fs/ocfs2/suballoc.c:776 ocfs2_reserve_new_metadata_blocks+0x34c/0x7d8 fs/ocfs2/suballoc.c:978 ocfs2_expand_inline_dir fs/ocfs2/dir.c:2838 [inline] ocfs2_extend_dir+0x96c/0x390c fs/ocfs2/dir.c:3200 ocfs2_prepare_dir_for_insert+0x25c0/0x4408 fs/ocfs2/dir.c:4321 ocfs2_rename+0x140c/0x2e98 fs/ocfs2/namei.c:1478 vfs_rename+0x954/0xdcc fs/namei.c:4832 do_renameat2+0x74c/0xcdc fs/namei.c:4985 __do_sys_renameat2 fs/namei.c:5018 [inline] __se_sys_renameat2 fs/namei.c:5015 [inline] __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5015 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 (syz.3.68,4421,0):ocfs2_rename:1687 ERROR: status = -39