====================================================== WARNING: possible circular locking dependency detected 6.1.53-syzkaller #0 Not tainted ------------------------------------------------------ kworker/u4:14/3997 is trying to acquire lock: ffff888076f78940 (&rl->lock){++++}-{3:3}, at: ntfs_read_block fs/ntfs/aops.c:248 [inline] ffff888076f78940 (&rl->lock){++++}-{3:3}, at: ntfs_read_folio+0x14c9/0x29d0 fs/ntfs/aops.c:436 but task is already holding lock: ffff888076f78190 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x48/0x630 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}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 __mutex_lock_common+0x1d4/0x2520 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799 map_mft_record+0x48/0x630 fs/ntfs/mft.c:154 ntfs_map_runlist_nolock+0x4b4/0x1790 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_read_folio+0x16fe/0x29d0 fs/ntfs/aops.c:436 read_pages+0x5f2/0x830 mm/readahead.c:181 page_cache_ra_unbounded+0x68b/0x7b0 mm/readahead.c:270 page_cache_sync_readahead include/linux/pagemap.h:1213 [inline] filemap_get_pages mm/filemap.c:2582 [inline] filemap_read+0x7fa/0x31d0 mm/filemap.c:2676 __kernel_read+0x41e/0x8a0 fs/read_write.c:428 integrity_kernel_read+0xac/0xf0 security/integrity/iint.c:202 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+0xa57/0x1c00 security/integrity/ima/ima_crypto.c:573 ima_collect_measurement+0x4d4/0x970 security/integrity/ima/ima_api.c:292 process_measurement+0x1018/0x1cf0 security/integrity/ima/ima_main.c:337 ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:520 do_open fs/namei.c:3559 [inline] path_openat+0x2687/0x2e60 fs/namei.c:3714 do_filp_open+0x230/0x480 fs/namei.c:3741 do_sys_openat2+0x13b/0x500 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_openat fs/open.c:1350 [inline] __se_sys_openat fs/open.c:1345 [inline] __x64_sys_openat+0x243/0x290 fs/open.c:1345 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&rl->lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3824 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5048 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 down_read+0x43/0x2e0 kernel/locking/rwsem.c:1520 ntfs_read_block fs/ntfs/aops.c:248 [inline] ntfs_read_folio+0x14c9/0x29d0 fs/ntfs/aops.c:436 filemap_read_folio+0x199/0x780 mm/filemap.c:2407 do_read_cache_folio+0x2ee/0x810 mm/filemap.c:3535 do_read_cache_page+0x32/0x220 mm/filemap.c:3577 read_mapping_page include/linux/pagemap.h:756 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0x25b/0x1ad0 fs/ntfs/mft.c:480 write_mft_record_nolock+0x1151/0x18d0 fs/ntfs/mft.c:787 write_mft_record+0x149/0x310 fs/ntfs/mft.h:95 __ntfs_write_inode+0x6ff/0xbb0 fs/ntfs/inode.c:3050 write_inode fs/fs-writeback.c:1443 [inline] __writeback_single_inode+0x67d/0x11e0 fs/fs-writeback.c:1655 writeback_sb_inodes+0xc21/0x1ac0 fs/fs-writeback.c:1881 wb_writeback+0x49d/0xe10 fs/fs-writeback.c:2055 wb_do_writeback fs/fs-writeback.c:2198 [inline] wb_workfn+0x427/0x1020 fs/fs-writeback.c:2238 process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2292 worker_thread+0xa5f/0x1210 kernel/workqueue.c:2439 kthread+0x26e/0x300 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 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:14/3997: #0: ffff888014ab6938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x77a/0x11f0 #1: ffffc90006fafd20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7bd/0x11f0 kernel/workqueue.c:2267 #2: ffff888076f78190 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x48/0x630 fs/ntfs/mft.c:154 stack backtrace: CPU: 1 PID: 3997 Comm: kworker/u4:14 Not tainted 6.1.53-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023 Workqueue: writeback wb_workfn (flush-7:0) Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 check_noncircular+0x2fa/0x3b0 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3824 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5048 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 down_read+0x43/0x2e0 kernel/locking/rwsem.c:1520 ntfs_read_block fs/ntfs/aops.c:248 [inline] ntfs_read_folio+0x14c9/0x29d0 fs/ntfs/aops.c:436 filemap_read_folio+0x199/0x780 mm/filemap.c:2407 do_read_cache_folio+0x2ee/0x810 mm/filemap.c:3535 do_read_cache_page+0x32/0x220 mm/filemap.c:3577 read_mapping_page include/linux/pagemap.h:756 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0x25b/0x1ad0 fs/ntfs/mft.c:480 write_mft_record_nolock+0x1151/0x18d0 fs/ntfs/mft.c:787 write_mft_record+0x149/0x310 fs/ntfs/mft.h:95 __ntfs_write_inode+0x6ff/0xbb0 fs/ntfs/inode.c:3050 write_inode fs/fs-writeback.c:1443 [inline] __writeback_single_inode+0x67d/0x11e0 fs/fs-writeback.c:1655 writeback_sb_inodes+0xc21/0x1ac0 fs/fs-writeback.c:1881 wb_writeback+0x49d/0xe10 fs/fs-writeback.c:2055 wb_do_writeback fs/fs-writeback.c:2198 [inline] wb_workfn+0x427/0x1020 fs/fs-writeback.c:2238 process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2292 worker_thread+0xa5f/0x1210 kernel/workqueue.c:2439 kthread+0x26e/0x300 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306