====================================================== WARNING: possible circular locking dependency detected 6.14.0-syzkaller-11270-g08733088b566 #0 Not tainted ------------------------------------------------------ syz.0.620/7899 is trying to acquire lock: ffff88805591cda0 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}, at: ocfs2_page_mkwrite+0x30f/0xd80 fs/ocfs2/mmap.c:142 but task is already holding lock: ffff888078d20518 (sb_pagefaults#2){.+.+}-{0:0}, at: do_page_mkwrite+0x17a/0x380 mm/memory.c:3253 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sb_pagefaults#2){.+.+}-{0:0}: 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+0x1d5/0xd80 fs/ocfs2/mmap.c:122 do_page_mkwrite+0x17a/0x380 mm/memory.c:3253 wp_page_shared mm/memory.c:3654 [inline] do_wp_page+0xc47/0x4670 mm/memory.c:3804 handle_pte_fault mm/memory.c:5906 [inline] __handle_mm_fault+0x1ae0/0x2a50 mm/memory.c:6033 handle_mm_fault+0x404/0xae0 mm/memory.c:6202 do_user_addr_fault+0x7a9/0x1430 arch/x86/mm/fault.c:1388 handle_page_fault arch/x86/mm/fault.c:1480 [inline] exc_page_fault+0x5c/0xc0 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}: __might_fault mm/memory.c:6958 [inline] __might_fault+0x113/0x190 mm/memory.c:6952 _inline_copy_to_user include/linux/uaccess.h:192 [inline] _copy_to_user+0x2d/0xd0 lib/usercopy.c:26 copy_to_user include/linux/uaccess.h:225 [inline] fiemap_fill_next_extent+0x239/0x390 fs/ioctl.c:145 ocfs2_fiemap_inline fs/ocfs2/extent_map.c:735 [inline] ocfs2_fiemap+0x91e/0xd00 fs/ocfs2/extent_map.c:772 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x404/0x1990 fs/ioctl.c:840 __do_sys_ioctl fs/ioctl.c:904 [inline] __se_sys_ioctl fs/ioctl.c:892 [inline] __x64_sys_ioctl+0x11d/0x200 fs/ioctl.c:892 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x260 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 kernel/locking/lockdep.c:3909 [inline] __lock_acquire+0x1173/0x1ba0 kernel/locking/lockdep.c:5235 lock_acquire kernel/locking/lockdep.c:5866 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5823 down_write+0x92/0x200 kernel/locking/rwsem.c:1577 ocfs2_page_mkwrite+0x30f/0xd80 fs/ocfs2/mmap.c:142 do_page_mkwrite+0x17a/0x380 mm/memory.c:3253 wp_page_shared mm/memory.c:3654 [inline] do_wp_page+0xc47/0x4670 mm/memory.c:3804 handle_pte_fault mm/memory.c:5906 [inline] __handle_mm_fault+0x1ae0/0x2a50 mm/memory.c:6033 handle_mm_fault+0x404/0xae0 mm/memory.c:6202 do_user_addr_fault+0x7a9/0x1430 arch/x86/mm/fault.c:1388 handle_page_fault arch/x86/mm/fault.c:1480 [inline] exc_page_fault+0x5c/0xc0 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#2 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(sb_pagefaults#2); lock(&mm->mmap_lock); lock(sb_pagefaults#2); lock(&ocfs2_file_ip_alloc_sem_key); *** DEADLOCK *** 2 locks held by syz.0.620/7899: #0: ffff88801319c7e0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_trylock include/linux/mmap_lock.h:209 [inline] #0: ffff88801319c7e0 (&mm->mmap_lock){++++}-{4:4}, at: get_mmap_lock_carefully mm/memory.c:6239 [inline] #0: ffff88801319c7e0 (&mm->mmap_lock){++++}-{4:4}, at: lock_mm_and_find_vma+0x35/0x6e0 mm/memory.c:6299 #1: ffff888078d20518 (sb_pagefaults#2){.+.+}-{0:0}, at: do_page_mkwrite+0x17a/0x380 mm/memory.c:3253 stack backtrace: CPU: 0 UID: 0 PID: 7899 Comm: syz.0.620 Not tainted 6.14.0-syzkaller-11270-g08733088b566 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x275/0x350 kernel/locking/lockdep.c:2079 check_noncircular+0x14c/0x170 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 kernel/locking/lockdep.c:3909 [inline] __lock_acquire+0x1173/0x1ba0 kernel/locking/lockdep.c:5235 lock_acquire kernel/locking/lockdep.c:5866 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5823 down_write+0x92/0x200 kernel/locking/rwsem.c:1577 ocfs2_page_mkwrite+0x30f/0xd80 fs/ocfs2/mmap.c:142 do_page_mkwrite+0x17a/0x380 mm/memory.c:3253 wp_page_shared mm/memory.c:3654 [inline] do_wp_page+0xc47/0x4670 mm/memory.c:3804 handle_pte_fault mm/memory.c:5906 [inline] __handle_mm_fault+0x1ae0/0x2a50 mm/memory.c:6033 handle_mm_fault+0x404/0xae0 mm/memory.c:6202 do_user_addr_fault+0x7a9/0x1430 arch/x86/mm/fault.c:1388 handle_page_fault arch/x86/mm/fault.c:1480 [inline] exc_page_fault+0x5c/0xc0 arch/x86/mm/fault.c:1538 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 RIP: 0033:0x7ff062b5471b Code: fa 10 73 2d 83 fa 08 73 46 83 fa 04 73 16 83 fa 01 7c 10 8a 0e 74 0a 0f b7 74 16 fe 66 89 74 17 fe 88 0f c3 8b 4c 16 fc 8b 36 <89> 4c 17 fc 89 37 c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 RSP: 002b:00007ffd9bffb918 EFLAGS: 00010202 RAX: 0000200000000040 RBX: 0000000000000004 RCX: 0000000000347478 RDX: 0000000000000005 RSI: 0000000034747865 RDI: 0000200000000040 RBP: 00007ff062da7ba0 R08: 00007ff062a00000 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000000009 R12: 00007ff062da5fac R13: 00007ff062da5fa0 R14: fffffffffffffffe R15: 00007ffd9bffba30