====================================================== WARNING: possible circular locking dependency detected 6.15.0-rc5-syzkaller-00123-g2c89c1b655c0 #0 Not tainted ------------------------------------------------------ syz.1.431/10535 is trying to acquire lock: ffff888058444da0 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}, at: ocfs2_page_mkwrite+0x2ff/0xc40 fs/ocfs2/mmap.c:142 but task is already holding lock: ffff888027054518 (sb_pagefaults#9){.+.+}-{0:0}, at: do_page_mkwrite+0x14a/0x310 mm/memory.c:3287 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sb_pagefaults#9){.+.+}-{0:0}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 percpu_down_read include/linux/percpu-rwsem.h:52 [inline] __sb_start_write include/linux/fs.h:1783 [inline] sb_start_pagefault include/linux/fs.h:1948 [inline] ocfs2_page_mkwrite+0x1da/0xc40 fs/ocfs2/mmap.c:122 do_page_mkwrite+0x14a/0x310 mm/memory.c:3287 do_shared_fault mm/memory.c:5594 [inline] do_fault mm/memory.c:5656 [inline] do_pte_missing mm/memory.c:4160 [inline] handle_pte_fault mm/memory.c:5997 [inline] __handle_mm_fault+0x18d2/0x5380 mm/memory.c:6140 handle_mm_fault+0x2d5/0x7f0 mm/memory.c:6309 do_user_addr_fault+0x764/0x1390 arch/x86/mm/fault.c:1388 handle_page_fault arch/x86/mm/fault.c:1480 [inline] exc_page_fault+0x68/0x110 arch/x86/mm/fault.c:1538 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 -> #1 (&mm->mmap_lock){++++}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 __might_fault+0xcc/0x130 mm/memory.c:7151 _inline_copy_to_user include/linux/uaccess.h:192 [inline] _copy_to_user+0x2c/0xb0 lib/usercopy.c:26 copy_to_user include/linux/uaccess.h:225 [inline] fiemap_fill_next_extent+0x1c0/0x390 fs/ioctl.c:145 ocfs2_fiemap_inline fs/ocfs2/extent_map.c:735 [inline] ocfs2_fiemap+0x9dc/0xc90 fs/ocfs2/extent_map.c:772 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1638/0x1eb0 fs/ioctl.c:840 __do_sys_ioctl fs/ioctl.c:904 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:892 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3909 __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 down_write+0x96/0x1f0 kernel/locking/rwsem.c:1577 ocfs2_page_mkwrite+0x2ff/0xc40 fs/ocfs2/mmap.c:142 do_page_mkwrite+0x14a/0x310 mm/memory.c:3287 do_shared_fault mm/memory.c:5594 [inline] do_fault mm/memory.c:5656 [inline] do_pte_missing mm/memory.c:4160 [inline] handle_pte_fault mm/memory.c:5997 [inline] __handle_mm_fault+0x18d2/0x5380 mm/memory.c:6140 handle_mm_fault+0x2d5/0x7f0 mm/memory.c:6309 do_user_addr_fault+0x764/0x1390 arch/x86/mm/fault.c:1388 handle_page_fault arch/x86/mm/fault.c:1480 [inline] exc_page_fault+0x68/0x110 arch/x86/mm/fault.c:1538 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 other info that might help us debug this: Chain exists of: &ocfs2_file_ip_alloc_sem_key --> &mm->mmap_lock --> sb_pagefaults#9 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(sb_pagefaults#9); lock(&mm->mmap_lock); lock(sb_pagefaults#9); lock(&ocfs2_file_ip_alloc_sem_key); *** DEADLOCK *** 2 locks held by syz.1.431/10535: #0: ffff88807f09bde0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_trylock include/linux/mmap_lock.h:203 [inline] #0: ffff88807f09bde0 (&mm->mmap_lock){++++}-{4:4}, at: get_mmap_lock_carefully mm/memory.c:6346 [inline] #0: ffff88807f09bde0 (&mm->mmap_lock){++++}-{4:4}, at: lock_mm_and_find_vma+0x32/0x300 mm/memory.c:6406 #1: ffff888027054518 (sb_pagefaults#9){.+.+}-{0:0}, at: do_page_mkwrite+0x14a/0x310 mm/memory.c:3287 stack backtrace: CPU: 1 UID: 0 PID: 10535 Comm: syz.1.431 Not tainted 6.15.0-rc5-syzkaller-00123-g2c89c1b655c0 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/29/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2079 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2211 check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3909 __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 down_write+0x96/0x1f0 kernel/locking/rwsem.c:1577 ocfs2_page_mkwrite+0x2ff/0xc40 fs/ocfs2/mmap.c:142 do_page_mkwrite+0x14a/0x310 mm/memory.c:3287 do_shared_fault mm/memory.c:5594 [inline] do_fault mm/memory.c:5656 [inline] do_pte_missing mm/memory.c:4160 [inline] handle_pte_fault mm/memory.c:5997 [inline] __handle_mm_fault+0x18d2/0x5380 mm/memory.c:6140 handle_mm_fault+0x2d5/0x7f0 mm/memory.c:6309 do_user_addr_fault+0x764/0x1390 arch/x86/mm/fault.c:1388 handle_page_fault arch/x86/mm/fault.c:1480 [inline] exc_page_fault+0x68/0x110 arch/x86/mm/fault.c:1538 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 RIP: 0033:0x7f2f9da54fe1 Code: 48 8b 54 24 08 48 85 d2 74 17 8b 44 24 18 0f c8 89 c0 48 89 44 24 18 48 83 fa 01 0f 85 b3 01 00 00 48 8b 44 24 10 8b 54 24 18 <89> 10 e9 15 fd ff ff 48 8b 44 24 10 8b 10 48 8b 44 24 08 48 85 c0 RSP: 002b:00007ffcdf3efd50 EFLAGS: 00010246 RAX: 00002000000000c4 RBX: 0000000000000004 RCX: 0000000000000000 RDX: 0000000000009971 RSI: 0000000000000000 RDI: 000055556c4743c8 RBP: 00007ffcdf3efe58 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000002 R12: 00007f2f9ddb5fac R13: 00007f2f9ddb5fa0 R14: fffffffffffffffe R15: 00007ffcdf3efea0