====================================================== WARNING: possible circular locking dependency detected 5.15.184-syzkaller #0 Not tainted ------------------------------------------------------ syz.3.293/5689 is trying to acquire lock: ffff88806139a2c0 (mapping.invalidate_lock#7){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:842 [inline] ffff88806139a2c0 (mapping.invalidate_lock#7){.+.+}-{3:3}, at: filemap_fault+0x68b/0x13b0 mm/filemap.c:3081 but task is already holding lock: ffff88801e4cc028 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline] ffff88801e4cc028 (&mm->mmap_lock){++++}-{3:3}, at: do_user_addr_fault+0x2b9/0xc80 arch/x86/mm/fault.c:1298 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&mm->mmap_lock){++++}-{3:3}: __might_fault+0xb3/0x110 mm/memory.c:5357 _copy_to_user+0x29/0x130 lib/usercopy.c:35 copy_to_user include/linux/uaccess.h:200 [inline] fiemap_fill_next_extent+0x19d/0x360 fs/ioctl.c:144 ni_fiemap+0x878/0xc20 fs/ntfs3/frecord.c:1998 ntfs_fiemap+0xd7/0x130 fs/ntfs3/file.c:1233 ioctl_fiemap fs/ioctl.c:219 [inline] do_vfs_ioctl+0x1464/0x1de0 fs/ioctl.c:814 __do_sys_ioctl fs/ioctl.c:872 [inline] __se_sys_ioctl+0x83/0x170 fs/ioctl.c:860 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 (&ni->file.run_lock){.+.+}-{3:3}: down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498 attr_data_get_block+0x10d/0x1880 fs/ntfs3/attrib.c:831 ntfs_get_block_vbo+0x2f6/0xc60 fs/ntfs3/inode.c:591 do_mpage_readpage+0x820/0x1e30 fs/mpage.c:231 mpage_readahead+0x3a6/0x8a0 fs/mpage.c:389 read_pages+0x165/0x920 mm/readahead.c:130 page_cache_ra_unbounded+0x830/0x930 mm/readahead.c:239 page_cache_sync_readahead include/linux/pagemap.h:833 [inline] filemap_get_pages mm/filemap.c:2551 [inline] filemap_read+0x589/0x2480 mm/filemap.c:2634 __kernel_read+0x4eb/0x910 fs/read_write.c:443 integrity_kernel_read+0x86/0xd0 security/integrity/iint.c:228 ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:485 [inline] ima_calc_file_shash security/integrity/ima/ima_crypto.c:516 [inline] ima_calc_file_hash+0x1546/0x18e0 security/integrity/ima/ima_crypto.c:573 ima_collect_measurement+0x2ef/0x760 security/integrity/ima/ima_api.c:255 process_measurement+0xfb9/0x1a10 security/integrity/ima/ima_main.c:351 ima_file_check+0xc1/0x100 security/integrity/ima/ima_main.c:533 do_open fs/namei.c:3610 [inline] path_openat+0x2735/0x2f30 fs/namei.c:3742 do_filp_open+0x1b3/0x3e0 fs/namei.c:3769 do_sys_openat2+0x142/0x4a0 fs/open.c:1253 do_sys_open fs/open.c:1269 [inline] __do_sys_openat fs/open.c:1285 [inline] __se_sys_openat fs/open.c:1280 [inline] __x64_sys_openat+0x135/0x160 fs/open.c:1280 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 -> #0 (mapping.invalidate_lock#7){.+.+}-{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+0x2c33/0x7c60 kernel/locking/lockdep.c:5012 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623 down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498 filemap_invalidate_lock_shared include/linux/fs.h:842 [inline] filemap_fault+0x68b/0x13b0 mm/filemap.c:3081 __do_fault+0x141/0x330 mm/memory.c:3928 do_shared_fault mm/memory.c:4318 [inline] do_fault mm/memory.c:4396 [inline] handle_pte_fault mm/memory.c:4650 [inline] __handle_mm_fault mm/memory.c:4785 [inline] handle_mm_fault+0x1cdd/0x43c0 mm/memory.c:4883 do_user_addr_fault+0x489/0xc80 arch/x86/mm/fault.c:1357 handle_page_fault arch/x86/mm/fault.c:1445 [inline] exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1501 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:606 other info that might help us debug this: Chain exists of: mapping.invalidate_lock#7 --> &ni->file.run_lock --> &mm->mmap_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&mm->mmap_lock); lock(&ni->file.run_lock); lock(&mm->mmap_lock); lock(mapping.invalidate_lock#7); *** DEADLOCK *** 1 lock held by syz.3.293/5689: #0: ffff88801e4cc028 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline] #0: ffff88801e4cc028 (&mm->mmap_lock){++++}-{3:3}, at: do_user_addr_fault+0x2b9/0xc80 arch/x86/mm/fault.c:1298 stack backtrace: CPU: 0 PID: 5689 Comm: syz.3.293 Not tainted 5.15.184-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106 check_noncircular+0x274/0x310 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+0x2c33/0x7c60 kernel/locking/lockdep.c:5012 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623 down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498 filemap_invalidate_lock_shared include/linux/fs.h:842 [inline] filemap_fault+0x68b/0x13b0 mm/filemap.c:3081 __do_fault+0x141/0x330 mm/memory.c:3928 do_shared_fault mm/memory.c:4318 [inline] do_fault mm/memory.c:4396 [inline] handle_pte_fault mm/memory.c:4650 [inline] __handle_mm_fault mm/memory.c:4785 [inline] handle_mm_fault+0x1cdd/0x43c0 mm/memory.c:4883 do_user_addr_fault+0x489/0xc80 arch/x86/mm/fault.c:1357 handle_page_fault arch/x86/mm/fault.c:1445 [inline] exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1501 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:606 RIP: 0033:0x7f92b40d56d8 Code: fc 89 37 c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 fa 7f 4c 17 f0 c3 66 0f 1f 84 00 00 00 00 00 48 8b 4c 16 f8 48 8b 36 <48> 89 37 48 89 4c 17 f8 c3 c5 fe 6f 54 16 e0 c5 fe 6f 5c 16 c0 c5 RSP: 002b:00007fff715c0b78 EFLAGS: 00010246 RAX: 0000200000000040 RBX: 0000000000000004 RCX: 0032656c69662f2e RDX: 0000000000000008 RSI: 0032656c69662f2e RDI: 0000200000000040 RBP: 00007f92b4336ba0 R08: 00007f92b3f7f000 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000000009 R12: 00007f92b4334fac R13: 00007f92b4334fa0 R14: fffffffffffffffe R15: 00007fff715c0c90