====================================================== WARNING: possible circular locking dependency detected 5.15.189-syzkaller #0 Not tainted ------------------------------------------------------ kworker/u4:5/4293 is trying to acquire lock: ffff888073f26400 (&rl->lock){++++}-{3:3}, at: ntfs_read_block fs/ntfs/aops.c:248 [inline] ffff888073f26400 (&rl->lock){++++}-{3:3}, at: ntfs_readpage+0x1277/0x2220 fs/ntfs/aops.c:435 but task is already holding lock: ffff888073f22290 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4e/0x620 fs/ntfs/mft.c:154 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ni->mrec_lock){+.+.}-{3:3}: __mutex_lock_common+0x1eb/0x2390 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 map_mft_record+0x4e/0x620 fs/ntfs/mft.c:154 ntfs_map_runlist_nolock+0x3f6/0x1760 fs/ntfs/attrib.c:91 ntfs_map_runlist+0x7e/0xa0 fs/ntfs/attrib.c:292 ntfs_read_block fs/ntfs/aops.c:283 [inline] ntfs_readpage+0x153d/0x2220 fs/ntfs/aops.c:435 read_pages+0x60d/0x920 mm/readahead.c:145 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 (&rl->lock){++++}-{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 ntfs_read_block fs/ntfs/aops.c:248 [inline] ntfs_readpage+0x1277/0x2220 fs/ntfs/aops.c:435 do_read_cache_page+0x8a1/0x1030 mm/filemap.c:-1 read_mapping_page include/linux/pagemap.h:515 [inline] ntfs_map_page+0x24/0x390 fs/ntfs/aops.h:75 ntfs_sync_mft_mirror+0x24a/0x19e0 fs/ntfs/mft.c:480 write_mft_record_nolock+0x1223/0x17e0 fs/ntfs/mft.c:787 write_mft_record fs/ntfs/mft.h:95 [inline] __ntfs_write_inode+0x7cb/0xdc0 fs/ntfs/inode.c:3050 write_inode fs/fs-writeback.c:1495 [inline] __writeback_single_inode+0x6c3/0xda0 fs/fs-writeback.c:1705 writeback_sb_inodes+0x9fe/0x1610 fs/fs-writeback.c:1930 wb_writeback+0x443/0xb90 fs/fs-writeback.c:2104 wb_do_writeback fs/fs-writeback.c:2247 [inline] wb_workfn+0x423/0xe60 fs/fs-writeback.c:2288 process_one_work+0x863/0x1000 kernel/workqueue.c:2310 worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457 kthread+0x436/0x520 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->mrec_lock); lock(&rl->lock); lock(&ni->mrec_lock); lock(&rl->lock); *** DEADLOCK *** 3 locks held by kworker/u4:5/4293: #0: ffff88814359e138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1 #1: ffffc90004b57d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285 #2: ffff888073f22290 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4e/0x620 fs/ntfs/mft.c:154 stack backtrace: CPU: 0 PID: 4293 Comm: kworker/u4:5 Not tainted 5.15.189-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Workqueue: writeback wb_workfn (flush-7:1) 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 ntfs_read_block fs/ntfs/aops.c:248 [inline] ntfs_readpage+0x1277/0x2220 fs/ntfs/aops.c:435 do_read_cache_page+0x8a1/0x1030 mm/filemap.c:-1 read_mapping_page include/linux/pagemap.h:515 [inline] ntfs_map_page+0x24/0x390 fs/ntfs/aops.h:75 ntfs_sync_mft_mirror+0x24a/0x19e0 fs/ntfs/mft.c:480 write_mft_record_nolock+0x1223/0x17e0 fs/ntfs/mft.c:787 write_mft_record fs/ntfs/mft.h:95 [inline] __ntfs_write_inode+0x7cb/0xdc0 fs/ntfs/inode.c:3050 write_inode fs/fs-writeback.c:1495 [inline] __writeback_single_inode+0x6c3/0xda0 fs/fs-writeback.c:1705 writeback_sb_inodes+0x9fe/0x1610 fs/fs-writeback.c:1930 wb_writeback+0x443/0xb90 fs/fs-writeback.c:2104 wb_do_writeback fs/fs-writeback.c:2247 [inline] wb_workfn+0x423/0xe60 fs/fs-writeback.c:2288 process_one_work+0x863/0x1000 kernel/workqueue.c:2310 worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457 kthread+0x436/0x520 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287