======================================================
WARNING: possible circular locking dependency detected
6.7.0-rc3-syzkaller-00284-g815fb87b7530 #0 Not tainted
------------------------------------------------------
kswapd0/86 is trying to acquire lock:
ffff88805b64c300 (&rl->lock){++++}-{3:3}, at: __ntfs_clear_inode+0x32/0x1f0 fs/ntfs/inode.c:2189
but task is already holding lock:
ffffffff8da12140 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat mm/vmscan.c:6716 [inline]
ffffffff8da12140 (fs_reclaim){+.+.}-{0:0}, at: kswapd+0xb38/0x2f50 mm/vmscan.c:7088
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (fs_reclaim){+.+.}-{0:0}:
lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754
__fs_reclaim_acquire mm/page_alloc.c:3693 [inline]
fs_reclaim_acquire+0x87/0x120 mm/page_alloc.c:3707
might_alloc include/linux/sched/mm.h:303 [inline]
prepare_alloc_pages+0x147/0x5b0 mm/page_alloc.c:4339
__alloc_pages+0x165/0x680 mm/page_alloc.c:4557
alloc_pages_mpol+0x3de/0x640 mm/mempolicy.c:2133
alloc_pages mm/mempolicy.c:2204 [inline]
folio_alloc+0x12a/0x330 mm/mempolicy.c:2211
filemap_alloc_folio+0xde/0x500 mm/filemap.c:974
do_read_cache_folio+0xed/0x810 mm/filemap.c:3655
do_read_cache_page+0x30/0x200 mm/filemap.c:3757
read_mapping_page include/linux/pagemap.h:871 [inline]
ntfs_map_page fs/ntfs/aops.h:75 [inline]
map_mft_record_page fs/ntfs/mft.c:73 [inline]
map_mft_record+0x1cd/0x630 fs/ntfs/mft.c:156
ntfs_read_locked_inode+0x199/0x4940 fs/ntfs/inode.c:550
ntfs_iget+0x113/0x190 fs/ntfs/inode.c:177
ntfs_lookup+0x28e/0xe00 fs/ntfs/namei.c:117
lookup_open fs/namei.c:3455 [inline]
open_last_lookups fs/namei.c:3546 [inline]
path_openat+0x1010/0x3290 fs/namei.c:3776
do_filp_open+0x234/0x490 fs/namei.c:3809
do_sys_openat2+0x13e/0x1d0 fs/open.c:1440
do_sys_open fs/open.c:1455 [inline]
__do_sys_openat fs/open.c:1471 [inline]
__se_sys_openat fs/open.c:1466 [inline]
__x64_sys_openat+0x247/0x290 fs/open.c:1466
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x45/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b
-> #1 (&ni->mrec_lock){+.+.}-{3:3}:
lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754
__mutex_lock_common kernel/locking/mutex.c:603 [inline]
__mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747
map_mft_record+0x4c/0x630 fs/ntfs/mft.c:154
ntfs_attr_extend_allocation+0x2d0/0x3ec0 fs/ntfs/attrib.c:2002
ntfs_prepare_file_for_write fs/ntfs/file.c:391 [inline]
ntfs_file_write_iter+0x37e/0x1970 fs/ntfs/file.c:1907
call_write_iter include/linux/fs.h:2020 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x792/0xb20 fs/read_write.c:584
ksys_write+0x1a0/0x2c0 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x45/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b
-> #0 (&rl->lock){++++}-{3:3}:
check_prev_add kernel/locking/lockdep.c:3134 [inline]
check_prevs_add kernel/locking/lockdep.c:3253 [inline]
validate_chain+0x1909/0x5ab0 kernel/locking/lockdep.c:3869
__lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5137
lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754
down_write+0x3a/0x50 kernel/locking/rwsem.c:1579
__ntfs_clear_inode+0x32/0x1f0 fs/ntfs/inode.c:2189
ntfs_evict_big_inode+0x2b1/0x480 fs/ntfs/inode.c:2278
evict+0x2a4/0x630 fs/inode.c:666
dispose_list fs/inode.c:699 [inline]
prune_icache_sb+0x239/0x2e0 fs/inode.c:884
super_cache_scan+0x382/0x4a0 fs/super.c:230
do_shrink_slab+0x6ed/0x1130 mm/shrinker.c:435
shrink_slab_memcg mm/shrinker.c:548 [inline]
shrink_slab+0x883/0x14c0 mm/shrinker.c:626
shrink_node_memcgs mm/vmscan.c:5814 [inline]
shrink_node+0x11d6/0x28c0 mm/vmscan.c:5847
kswapd_shrink_node mm/vmscan.c:6638 [inline]
balance_pgdat mm/vmscan.c:6828 [inline]
kswapd+0x1aab/0x2f50 mm/vmscan.c:7088
kthread+0x2d3/0x370 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
other info that might help us debug this:
Chain exists of:
&rl->lock --> &ni->mrec_lock --> fs_reclaim
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(fs_reclaim);
lock(&ni->mrec_lock);
lock(fs_reclaim);
lock(&rl->lock);
*** DEADLOCK ***
2 locks held by kswapd0/86:
#0: ffffffff8da12140 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat mm/vmscan.c:6716 [inline]
#0: ffffffff8da12140 (fs_reclaim){+.+.}-{0:0}, at: kswapd+0xb38/0x2f50 mm/vmscan.c:7088
#1: ffff8880532e40e0 (&type->s_umount_key#55){++++}-{3:3}, at: super_trylock_shared fs/super.c:610 [inline]
#1: ffff8880532e40e0 (&type->s_umount_key#55){++++}-{3:3}, at: super_cache_scan+0x94/0x4a0 fs/super.c:203
stack backtrace:
CPU: 1 PID: 86 Comm: kswapd0 Not tainted 6.7.0-rc3-syzkaller-00284-g815fb87b7530 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
check_noncircular+0x366/0x490 kernel/locking/lockdep.c:2187
check_prev_add kernel/locking/lockdep.c:3134 [inline]
check_prevs_add kernel/locking/lockdep.c:3253 [inline]
validate_chain+0x1909/0x5ab0 kernel/locking/lockdep.c:3869
__lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5137
lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754
down_write+0x3a/0x50 kernel/locking/rwsem.c:1579
__ntfs_clear_inode+0x32/0x1f0 fs/ntfs/inode.c:2189
ntfs_evict_big_inode+0x2b1/0x480 fs/ntfs/inode.c:2278
evict+0x2a4/0x630 fs/inode.c:666
dispose_list fs/inode.c:699 [inline]
prune_icache_sb+0x239/0x2e0 fs/inode.c:884
super_cache_scan+0x382/0x4a0 fs/super.c:230
do_shrink_slab+0x6ed/0x1130 mm/shrinker.c:435
shrink_slab_memcg mm/shrinker.c:548 [inline]
shrink_slab+0x883/0x14c0 mm/shrinker.c:626
shrink_node_memcgs mm/vmscan.c:5814 [inline]
shrink_node+0x11d6/0x28c0 mm/vmscan.c:5847
kswapd_shrink_node mm/vmscan.c:6638 [inline]
balance_pgdat mm/vmscan.c:6828 [inline]
kswapd+0x1aab/0x2f50 mm/vmscan.c:7088
kthread+0x2d3/0x370 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
</TASK>