======================================================
WARNING: possible circular locking dependency detected
6.8.0-rc2-syzkaller-00043-g2a6526c4f389 #0 Not tainted
------------------------------------------------------
syz-executor.3/30346 is trying to acquire lock:
ffff888038edf510 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4c/0x630 fs/ntfs/mft.c:154

but task is already holding lock:
ffff888038edf480 (&rl->lock){++++}-{3:3}, at: ntfs_truncate+0x1e7/0x2880 fs/ntfs/inode.c:2378

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&rl->lock){++++}-{3:3}:
       lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754
       down_read+0xb1/0xa40 kernel/locking/rwsem.c:1526
       ntfs_read_block fs/ntfs/aops.c:242 [inline]
       ntfs_read_folio+0x1308/0x23e0 fs/ntfs/aops.c:430
       filemap_read_folio+0x19c/0x780 mm/filemap.c:2324
       do_read_cache_folio+0x134/0x810 mm/filemap.c:3703
       do_read_cache_page+0x30/0x200 mm/filemap.c:3769
       read_mapping_page include/linux/pagemap.h:888 [inline]
       ntfs_map_page fs/ntfs/aops.h:75 [inline]
       ntfs_sync_mft_mirror+0x25f/0x1ae0 fs/ntfs/mft.c:480
       write_mft_record_nolock+0x1155/0x18f0 fs/ntfs/mft.c:787
       write_mft_record+0x149/0x310 fs/ntfs/mft.h:95
       __ntfs_write_inode+0x703/0xbb0 fs/ntfs/inode.c:3052
       write_inode fs/fs-writeback.c:1473 [inline]
       __writeback_single_inode+0x69b/0xfc0 fs/fs-writeback.c:1690
       writeback_sb_inodes+0x8e3/0x1220 fs/fs-writeback.c:1916
       __writeback_inodes_wb+0x11b/0x260 fs/fs-writeback.c:1987
       wb_writeback+0x461/0xc70 fs/fs-writeback.c:2094
       wb_check_start_all fs/fs-writeback.c:2220 [inline]
       wb_do_writeback fs/fs-writeback.c:2246 [inline]
       wb_workfn+0x95b/0xfb0 fs/fs-writeback.c:2279
       process_one_work kernel/workqueue.c:2633 [inline]
       process_scheduled_works+0x90f/0x1420 kernel/workqueue.c:2706
       worker_thread+0xa5f/0x1000 kernel/workqueue.c:2787
       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

-> #0 (&ni->mrec_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
       __mutex_lock_common kernel/locking/mutex.c:608 [inline]
       __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:752
       map_mft_record+0x4c/0x630 fs/ntfs/mft.c:154
       ntfs_truncate+0x267/0x2880 fs/ntfs/inode.c:2383
       ntfs_truncate_vfs fs/ntfs/inode.c:2864 [inline]
       ntfs_setattr+0x3f5/0x4d0 fs/ntfs/inode.c:2916
       notify_change+0xb99/0xe60 fs/attr.c:499
       do_truncate+0x220/0x300 fs/open.c:66
       do_sys_ftruncate+0x2f3/0x390 fs/open.c:194
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf5/0x230 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x63/0x6b

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&rl->lock);
                               lock(&ni->mrec_lock);
                               lock(&rl->lock);
  lock(&ni->mrec_lock);

 *** DEADLOCK ***

3 locks held by syz-executor.3/30346:
 #0: ffff888039fe8420 (sb_writers#32){.+.+}-{0:0}, at: do_sys_ftruncate+0x258/0x390 fs/open.c:191
 #1: ffff888038edf7f0 (&sb->s_type->i_mutex_key#38){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:802 [inline]
 #1: ffff888038edf7f0 (&sb->s_type->i_mutex_key#38){+.+.}-{3:3}, at: do_truncate+0x20c/0x300 fs/open.c:64
 #2: ffff888038edf480 (&rl->lock){++++}-{3:3}, at: ntfs_truncate+0x1e7/0x2880 fs/ntfs/inode.c:2378

stack backtrace:
CPU: 0 PID: 30346 Comm: syz-executor.3 Not tainted 6.8.0-rc2-syzkaller-00043-g2a6526c4f389 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/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
 __mutex_lock_common kernel/locking/mutex.c:608 [inline]
 __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:752
 map_mft_record+0x4c/0x630 fs/ntfs/mft.c:154
 ntfs_truncate+0x267/0x2880 fs/ntfs/inode.c:2383
 ntfs_truncate_vfs fs/ntfs/inode.c:2864 [inline]
 ntfs_setattr+0x3f5/0x4d0 fs/ntfs/inode.c:2916
 notify_change+0xb99/0xe60 fs/attr.c:499
 do_truncate+0x220/0x300 fs/open.c:66
 do_sys_ftruncate+0x2f3/0x390 fs/open.c:194
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf5/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7ff564c7dda9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff565a010c8 EFLAGS: 00000246 ORIG_RAX: 000000000000004d
RAX: ffffffffffffffda RBX: 00007ff564dabf80 RCX: 00007ff564c7dda9
RDX: 0000000000000000 RSI: 000000000000f5d1 RDI: 0000000000000005
RBP: 00007ff564cca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007ff564dabf80 R15: 00007fffc92316f8
 </TASK>