====================================================== WARNING: possible circular locking dependency detected 6.2.0-rc6-syzkaller-00083-ge7368fd30165 #0 Not tainted ------------------------------------------------------ kworker/u4:3/51 is trying to acquire lock: ffff88803ac24300 (&rl->lock){++++}-{3:3}, at: ntfs_read_block+0x91a/0x22e0 fs/ntfs/aops.c:248 but task is already holding lock: ffff88802fa2dc50 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x46/0x610 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+0x182/0x3c0 kernel/locking/lockdep.c:5668 __mutex_lock_common+0x1bd/0x26e0 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+0x46/0x610 fs/ntfs/mft.c:154 ntfs_map_runlist_nolock+0x469/0x16e0 fs/ntfs/attrib.c:91 ntfs_map_runlist+0x7e/0xa0 fs/ntfs/attrib.c:292 ntfs_read_block+0xbd8/0x22e0 fs/ntfs/aops.c:283 read_pages+0x74b/0x9c0 mm/readahead.c:181 page_cache_ra_unbounded+0x703/0x820 mm/readahead.c:270 page_cache_sync_readahead include/linux/pagemap.h:1210 [inline] filemap_get_pages+0x465/0x10d0 mm/filemap.c:2600 filemap_read+0x3cf/0xea0 mm/filemap.c:2694 __kernel_read+0x3fc/0x830 fs/read_write.c:428 integrity_kernel_read+0xac/0xf0 security/integrity/iint.c:199 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+0x178f/0x1ca0 security/integrity/ima/ima_crypto.c:573 ima_collect_measurement+0x444/0x8c0 security/integrity/ima/ima_api.c:292 process_measurement+0xf41/0x1bc0 security/integrity/ima/ima_main.c:339 ima_file_check+0xd8/0x130 security/integrity/ima/ima_main.c:519 do_open fs/namei.c:3559 [inline] path_openat+0x2600/0x2dd0 fs/namei.c:3714 do_filp_open+0x264/0x4f0 fs/namei.c:3741 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_openat fs/open.c:1342 [inline] __se_sys_openat fs/open.c:1337 [inline] __x64_sys_openat+0x243/0x290 fs/open.c:1337 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:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain+0x1898/0x6ae0 kernel/locking/lockdep.c:3831 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 down_read+0x39/0x50 kernel/locking/rwsem.c:1509 ntfs_read_block+0x91a/0x22e0 fs/ntfs/aops.c:248 filemap_read_folio+0x187/0x7d0 mm/filemap.c:2426 do_read_cache_folio+0x2d3/0x790 mm/filemap.c:3553 do_read_cache_page mm/filemap.c:3595 [inline] read_cache_page+0x56/0x270 mm/filemap.c:3604 read_mapping_page include/linux/pagemap.h:755 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0x21a/0x1df0 fs/ntfs/mft.c:480 write_mft_record_nolock+0x1213/0x1930 fs/ntfs/mft.c:787 write_mft_record fs/ntfs/mft.h:95 [inline] __ntfs_write_inode+0x721/0xc90 fs/ntfs/inode.c:3050 write_inode fs/fs-writeback.c:1451 [inline] __writeback_single_inode+0x4d6/0x670 fs/fs-writeback.c:1663 writeback_sb_inodes+0x812/0x1050 fs/fs-writeback.c:1889 wb_writeback+0x41f/0x7b0 fs/fs-writeback.c:2063 wb_do_writeback fs/fs-writeback.c:2206 [inline] wb_workfn+0x3cb/0xef0 fs/fs-writeback.c:2246 process_one_work+0x877/0xdb0 kernel/workqueue.c:2289 worker_thread+0xb14/0x1330 kernel/workqueue.c:2436 kthread+0x266/0x300 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 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:3/51: #0: ffff888017dac938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7f2/0xdb0 #1: ffffc90000bc7d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x831/0xdb0 kernel/workqueue.c:2264 #2: ffff88802fa2dc50 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x46/0x610 fs/ntfs/mft.c:154 stack backtrace: CPU: 0 PID: 51 Comm: kworker/u4:3 Not tainted 6.2.0-rc6-syzkaller-00083-ge7368fd30165 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023 Workqueue: writeback wb_workfn (flush-7:5) Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x290 lib/dump_stack.c:106 check_noncircular+0x2cc/0x390 kernel/locking/lockdep.c:2177 check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain+0x1898/0x6ae0 kernel/locking/lockdep.c:3831 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 down_read+0x39/0x50 kernel/locking/rwsem.c:1509 ntfs_read_block+0x91a/0x22e0 fs/ntfs/aops.c:248 filemap_read_folio+0x187/0x7d0 mm/filemap.c:2426 do_read_cache_folio+0x2d3/0x790 mm/filemap.c:3553 do_read_cache_page mm/filemap.c:3595 [inline] read_cache_page+0x56/0x270 mm/filemap.c:3604 read_mapping_page include/linux/pagemap.h:755 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0x21a/0x1df0 fs/ntfs/mft.c:480 write_mft_record_nolock+0x1213/0x1930 fs/ntfs/mft.c:787 write_mft_record fs/ntfs/mft.h:95 [inline] __ntfs_write_inode+0x721/0xc90 fs/ntfs/inode.c:3050 write_inode fs/fs-writeback.c:1451 [inline] __writeback_single_inode+0x4d6/0x670 fs/fs-writeback.c:1663 writeback_sb_inodes+0x812/0x1050 fs/fs-writeback.c:1889 wb_writeback+0x41f/0x7b0 fs/fs-writeback.c:2063 wb_do_writeback fs/fs-writeback.c:2206 [inline] wb_workfn+0x3cb/0xef0 fs/fs-writeback.c:2246 process_one_work+0x877/0xdb0 kernel/workqueue.c:2289 worker_thread+0xb14/0x1330 kernel/workqueue.c:2436 kthread+0x266/0x300 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308