====================================================== WARNING: possible circular locking dependency detected 6.16.0-rc1-syzkaller-00010-g2c4a1f3fe03e #0 Not tainted ------------------------------------------------------ syz.1.22/6126 is trying to acquire lock: ffff8880586bbf60 (&oi->ip_alloc_sem){++++}-{4:4}, at: ocfs2_read_folio+0x353/0x970 fs/ocfs2/aops.c:287 but task is already holding lock: ffff8880586bc460 (mapping.invalidate_lock#4){.+.+}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:932 [inline] ffff8880586bc460 (mapping.invalidate_lock#4){.+.+}-{4:4}, at: filemap_create_folio mm/filemap.c:2538 [inline] ffff8880586bc460 (mapping.invalidate_lock#4){.+.+}-{4:4}, at: filemap_get_pages+0xc29/0x1ea0 mm/filemap.c:2608 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (mapping.invalidate_lock#4){.+.+}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1524 filemap_invalidate_lock_shared include/linux/fs.h:932 [inline] filemap_fault+0x546/0x1200 mm/filemap.c:3400 ocfs2_fault+0xa4/0x3f0 fs/ocfs2/mmap.c:38 __do_fault+0x135/0x390 mm/memory.c:5189 do_read_fault mm/memory.c:5610 [inline] do_fault mm/memory.c:5744 [inline] do_pte_missing mm/memory.c:4251 [inline] handle_pte_fault mm/memory.c:6089 [inline] __handle_mm_fault+0x37ed/0x5620 mm/memory.c:6232 handle_mm_fault+0x2d5/0x7f0 mm/memory.c:6401 do_user_addr_fault+0x764/0x1390 arch/x86/mm/fault.c:1387 handle_page_fault arch/x86/mm/fault.c:1476 [inline] exc_page_fault+0x76/0xf0 arch/x86/mm/fault.c:1532 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:5871 __might_fault+0xcc/0x130 mm/memory.c:6991 _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+0x888/0xc90 fs/ocfs2/extent_map.c:806 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x16d3/0x1990 fs/ioctl.c:841 __do_sys_ioctl fs/ioctl.c:905 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&oi->ip_alloc_sem){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1524 ocfs2_read_folio+0x353/0x970 fs/ocfs2/aops.c:287 filemap_read_folio+0x114/0x380 mm/filemap.c:2412 filemap_create_folio mm/filemap.c:2547 [inline] filemap_get_pages+0xd4e/0x1ea0 mm/filemap.c:2608 filemap_read+0x3f6/0x11a0 mm/filemap.c:2711 ocfs2_file_read_iter+0x3fa/0xa80 fs/ocfs2/file.c:2589 __kernel_read+0x469/0x8c0 fs/read_write.c:530 integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28 ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:480 [inline] ima_calc_file_shash security/integrity/ima/ima_crypto.c:511 [inline] ima_calc_file_hash+0x85e/0x16f0 security/integrity/ima/ima_crypto.c:568 ima_collect_measurement+0x428/0x8d0 security/integrity/ima/ima_api.c:293 process_measurement+0x1121/0x1a40 security/integrity/ima/ima_main.c:385 ima_file_check+0xd7/0x120 security/integrity/ima/ima_main.c:613 security_file_post_open+0xbb/0x290 security/security.c:3130 do_open fs/namei.c:3889 [inline] path_openat+0x2f26/0x3830 fs/namei.c:4046 do_filp_open+0x1fa/0x410 fs/namei.c:4073 do_sys_openat2+0x121/0x1c0 fs/open.c:1437 do_sys_open fs/open.c:1452 [inline] __do_sys_openat fs/open.c:1468 [inline] __se_sys_openat fs/open.c:1463 [inline] __x64_sys_openat+0x138/0x170 fs/open.c:1463 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Chain exists of: &oi->ip_alloc_sem --> &mm->mmap_lock --> mapping.invalidate_lock#4 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(mapping.invalidate_lock#4); lock(&mm->mmap_lock); lock(mapping.invalidate_lock#4); rlock(&oi->ip_alloc_sem); *** DEADLOCK *** 2 locks held by syz.1.22/6126: #0: ffff88807d4d6f48 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}, at: process_measurement+0x74b/0x1a40 security/integrity/ima/ima_main.c:279 #1: ffff8880586bc460 (mapping.invalidate_lock#4){.+.+}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:932 [inline] #1: ffff8880586bc460 (mapping.invalidate_lock#4){.+.+}-{4:4}, at: filemap_create_folio mm/filemap.c:2538 [inline] #1: ffff8880586bc460 (mapping.invalidate_lock#4){.+.+}-{4:4}, at: filemap_get_pages+0xc29/0x1ea0 mm/filemap.c:2608 stack backtrace: CPU: 1 UID: 0 PID: 6126 Comm: syz.1.22 Not tainted 6.16.0-rc1-syzkaller-00010-g2c4a1f3fe03e #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2046 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1524 ocfs2_read_folio+0x353/0x970 fs/ocfs2/aops.c:287 filemap_read_folio+0x114/0x380 mm/filemap.c:2412 filemap_create_folio mm/filemap.c:2547 [inline] filemap_get_pages+0xd4e/0x1ea0 mm/filemap.c:2608 filemap_read+0x3f6/0x11a0 mm/filemap.c:2711 ocfs2_file_read_iter+0x3fa/0xa80 fs/ocfs2/file.c:2589 __kernel_read+0x469/0x8c0 fs/read_write.c:530 integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28 ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:480 [inline] ima_calc_file_shash security/integrity/ima/ima_crypto.c:511 [inline] ima_calc_file_hash+0x85e/0x16f0 security/integrity/ima/ima_crypto.c:568 ima_collect_measurement+0x428/0x8d0 security/integrity/ima/ima_api.c:293 process_measurement+0x1121/0x1a40 security/integrity/ima/ima_main.c:385 ima_file_check+0xd7/0x120 security/integrity/ima/ima_main.c:613 security_file_post_open+0xbb/0x290 security/security.c:3130 do_open fs/namei.c:3889 [inline] path_openat+0x2f26/0x3830 fs/namei.c:4046 do_filp_open+0x1fa/0x410 fs/namei.c:4073 do_sys_openat2+0x121/0x1c0 fs/open.c:1437 do_sys_open fs/open.c:1452 [inline] __do_sys_openat fs/open.c:1468 [inline] __se_sys_openat fs/open.c:1463 [inline] __x64_sys_openat+0x138/0x170 fs/open.c:1463 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f070618e929 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f0707095038 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 00007f07063b6080 RCX: 00007f070618e929 RDX: 0000000000141042 RSI: 0000200000000040 RDI: ffffffffffffff9c RBP: 00007f0706210b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f07063b6080 R15: 00007ffc53a3dc38