====================================================== WARNING: possible circular locking dependency detected 6.5.0-rc4-syzkaller-00009-g4b954598a47b #0 Not tainted ------------------------------------------------------ kworker/u17:0/10 is trying to acquire lock: ffff8880425bd380 (&rl->lock){++++}-{3:3}, at: ntfs_sync_mft_mirror+0x19bb/0x1eb0 fs/ntfs/mft.c:536 but task is already holding lock: ffff888045660190 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4a/0x730 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}: __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x181/0x1340 kernel/locking/mutex.c:747 map_mft_record+0x4a/0x730 fs/ntfs/mft.c:154 ntfs_attr_extend_allocation+0x268/0x3830 fs/ntfs/attrib.c:2002 ntfs_prepare_file_for_write fs/ntfs/file.c:391 [inline] ntfs_file_write_iter+0xa98/0x1e00 fs/ntfs/file.c:1914 call_write_iter include/linux/fs.h:1871 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x650/0xe40 fs/read_write.c:584 ksys_write+0x12f/0x250 fs/read_write.c:637 do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline] __do_fast_syscall_32+0x61/0xe0 arch/x86/entry/common.c:178 do_fast_syscall_32+0x33/0x70 arch/x86/entry/common.c:203 entry_SYSENTER_compat_after_hwframe+0x70/0x82 -> #0 (&rl->lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3142 [inline] check_prevs_add kernel/locking/lockdep.c:3261 [inline] validate_chain kernel/locking/lockdep.c:3876 [inline] __lock_acquire+0x2e3d/0x5de0 kernel/locking/lockdep.c:5144 lock_acquire kernel/locking/lockdep.c:5761 [inline] lock_acquire+0x1ae/0x510 kernel/locking/lockdep.c:5726 down_read+0x9c/0x470 kernel/locking/rwsem.c:1520 ntfs_sync_mft_mirror+0x19bb/0x1eb0 fs/ntfs/mft.c:536 write_mft_record_nolock+0x1967/0x1d90 fs/ntfs/mft.c:787 write_mft_record+0x14b/0x380 fs/ntfs/mft.h:95 __ntfs_write_inode+0x91b/0xc30 fs/ntfs/inode.c:3050 write_inode fs/fs-writeback.c:1456 [inline] __writeback_single_inode+0xa81/0xe70 fs/fs-writeback.c:1668 writeback_sb_inodes+0x599/0x1010 fs/fs-writeback.c:1894 wb_writeback+0x2a5/0xa90 fs/fs-writeback.c:2070 wb_do_writeback fs/fs-writeback.c:2217 [inline] wb_workfn+0x29c/0xfd0 fs/fs-writeback.c:2257 process_one_work+0xaa2/0x16f0 kernel/workqueue.c:2597 worker_thread+0x687/0x1110 kernel/workqueue.c:2748 kthread+0x33a/0x430 kernel/kthread.c:389 ret_from_fork+0x2c/0x70 arch/x86/kernel/process.c:145 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304 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); rlock(&rl->lock); *** DEADLOCK *** 3 locks held by kworker/u17:0/10: #0: ffff888013750138 ((wq_completion)writeback){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:20 [inline] #0: ffff888013750138 ((wq_completion)writeback){+.+.}-{0:0}, at: raw_atomic64_set include/linux/atomic/atomic-arch-fallback.h:2608 [inline] #0: ffff888013750138 ((wq_completion)writeback){+.+.}-{0:0}, at: raw_atomic_long_set include/linux/atomic/atomic-long.h:79 [inline] #0: ffff888013750138 ((wq_completion)writeback){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:3196 [inline] #0: ffff888013750138 ((wq_completion)writeback){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:675 [inline] #0: ffff888013750138 ((wq_completion)writeback){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:702 [inline] #0: ffff888013750138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x96a/0x16f0 kernel/workqueue.c:2567 #1: ffffc900003c7d80 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x99e/0x16f0 kernel/workqueue.c:2571 #2: ffff888045660190 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4a/0x730 fs/ntfs/mft.c:154 stack backtrace: CPU: 2 PID: 10 Comm: kworker/u17:0 Not tainted 6.5.0-rc4-syzkaller-00009-g4b954598a47b #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 Workqueue: writeback wb_workfn (flush-7:2) Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106 check_noncircular+0x311/0x3f0 kernel/locking/lockdep.c:2195 check_prev_add kernel/locking/lockdep.c:3142 [inline] check_prevs_add kernel/locking/lockdep.c:3261 [inline] validate_chain kernel/locking/lockdep.c:3876 [inline] __lock_acquire+0x2e3d/0x5de0 kernel/locking/lockdep.c:5144 lock_acquire kernel/locking/lockdep.c:5761 [inline] lock_acquire+0x1ae/0x510 kernel/locking/lockdep.c:5726 down_read+0x9c/0x470 kernel/locking/rwsem.c:1520 ntfs_sync_mft_mirror+0x19bb/0x1eb0 fs/ntfs/mft.c:536 write_mft_record_nolock+0x1967/0x1d90 fs/ntfs/mft.c:787 write_mft_record+0x14b/0x380 fs/ntfs/mft.h:95 __ntfs_write_inode+0x91b/0xc30 fs/ntfs/inode.c:3050 write_inode fs/fs-writeback.c:1456 [inline] __writeback_single_inode+0xa81/0xe70 fs/fs-writeback.c:1668 writeback_sb_inodes+0x599/0x1010 fs/fs-writeback.c:1894 wb_writeback+0x2a5/0xa90 fs/fs-writeback.c:2070 wb_do_writeback fs/fs-writeback.c:2217 [inline] wb_workfn+0x29c/0xfd0 fs/fs-writeback.c:2257 process_one_work+0xaa2/0x16f0 kernel/workqueue.c:2597 worker_thread+0x687/0x1110 kernel/workqueue.c:2748 kthread+0x33a/0x430 kernel/kthread.c:389 ret_from_fork+0x2c/0x70 arch/x86/kernel/process.c:145 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304