======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.3.20/4939 is trying to acquire lock:
ffff888056c31a50 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4e/0x620 fs/ntfs/mft.c:154

but task is already holding lock:
ffff888056c319c0 (&rl->lock){++++}-{3:3}, at: ntfs_attr_extend_allocation+0x52b/0x42a0 fs/ntfs/attrib.c:2001

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&rl->lock){++++}-{3:3}
:
       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:1505 [inline]
       __writeback_single_inode+0x6c3/0xda0 fs/fs-writeback.c:1715
       writeback_sb_inodes+0x9fe/0x1610 fs/fs-writeback.c:1940
       wb_writeback+0x443/0xb90 fs/fs-writeback.c:2114
       wb_do_writeback fs/fs-writeback.c:2257 [inline]
       wb_workfn+0x423/0xe60 fs/fs-writeback.c:2298
       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

-> #0 (&ni->mrec_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
       __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_attr_extend_allocation+0x533/0x42a0 fs/ntfs/attrib.c:2002
       ntfs_prepare_file_for_write fs/ntfs/file.c:395 [inline]
       ntfs_file_write_iter+0x46e/0x1d60 fs/ntfs/file.c:1919
       do_iter_readv_writev+0x497/0x600 fs/read_write.c:-1
       do_iter_write+0x205/0x7b0 fs/read_write.c:855
       vfs_writev fs/read_write.c:928 [inline]
       do_pwritev+0x204/0x340 fs/read_write.c:1025
       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

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.3.20/4939:
 #0: ffff8880589ac460 (sb_writers#13){.+.+}-{0:0}, at: vfs_writev fs/read_write.c:927 [inline]
 #0: ffff8880589ac460 (sb_writers#13){.+.+}-{0:0}, at: do_pwritev+0x1f2/0x340 fs/read_write.c:1025
 #1: ffff888056c31d30 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #1: ffff888056c31d30 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_file_write_iter+0x7b/0x1d60 fs/ntfs/file.c:1916
 #2: ffff888056c319c0 (&rl->lock){++++}-{3:3}, at: ntfs_attr_extend_allocation+0x52b/0x42a0 fs/ntfs/attrib.c:2001

stack backtrace:
CPU: 0 PID: 4939 Comm: syz.3.20 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 <TASK>
 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
 __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_attr_extend_allocation+0x533/0x42a0 fs/ntfs/attrib.c:2002
 ntfs_prepare_file_for_write fs/ntfs/file.c:395 [inline]
 ntfs_file_write_iter+0x46e/0x1d60 fs/ntfs/file.c:1919
 do_iter_readv_writev+0x497/0x600 fs/read_write.c:-1
 do_iter_write+0x205/0x7b0 fs/read_write.c:855
 vfs_writev fs/read_write.c:928 [inline]
 do_pwritev+0x204/0x340 fs/read_write.c:1025
 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
RIP: 0033:0x7f1cfcf6ac29
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f1cfc5b9038 EFLAGS: 00000246 ORIG_RAX: 0000000000000128
RAX: ffffffffffffffda RBX: 00007f1cfd1b2090 RCX: 00007f1cfcf6ac29
RDX: 0000000000000002 RSI: 0000200000000140 RDI: 0000000000000006
RBP: 00007f1cfcfede41 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000002cbc R11: 0000000000000246 R12: 0000000000000000
R13: 00007f1cfd1b2128 R14: 00007f1cfd1b2090 R15: 00007ffef2c96078
 </TASK>