====================================================== WARNING: possible circular locking dependency detected 6.9.0-syzkaller-08284-gea5f6ad9ad96 #0 Not tainted ------------------------------------------------------ kworker/u8:18/11086 is trying to acquire lock: ffff88807ecfa128 (&wnd->rw_lock/1){+.+.}-{3:3}, at: ntfs_mark_rec_free+0x2f4/0x400 fs/ntfs3/fsntfs.c:742 but task is already holding lock: ffff88805c7434a0 (&ni->ni_lock#3){+.+.}-{3:3}, at: ni_trylock fs/ntfs3/ntfs_fs.h:1143 [inline] ffff88805c7434a0 (&ni->ni_lock#3){+.+.}-{3:3}, at: ni_write_inode+0x24a/0x2920 fs/ntfs3/frecord.c:3265 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ni->ni_lock#3){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 ntfs_set_state+0x1d2/0x6a0 fs/ntfs3/fsntfs.c:947 mi_read+0x5ca/0x660 fs/ntfs3/record.c:185 mi_format_new+0x3a1/0x580 fs/ntfs3/record.c:420 ni_add_subrecord+0xd1/0x4f0 fs/ntfs3/frecord.c:372 ntfs_look_free_mft+0x209/0xdd0 fs/ntfs3/fsntfs.c:715 ni_create_attr_list+0x90b/0x14f0 fs/ntfs3/frecord.c:876 ni_ins_attr_ext+0x236/0xae0 fs/ntfs3/frecord.c:974 ni_insert_attr+0x30b/0x860 fs/ntfs3/frecord.c:1141 ni_insert_resident+0xd2/0x3a0 fs/ntfs3/frecord.c:1525 ni_add_name+0x48d/0x820 fs/ntfs3/frecord.c:3047 ni_rename+0xa1/0x1a0 fs/ntfs3/frecord.c:3087 ntfs_rename+0x96f/0xf20 fs/ntfs3/namei.c:334 vfs_rename+0xf87/0x20a0 fs/namei.c:4887 do_renameat2+0xc54/0xdc0 fs/namei.c:5044 __do_sys_renameat2 fs/namei.c:5078 [inline] __se_sys_renameat2 fs/namei.c:5075 [inline] __x64_sys_renameat2+0xeb/0x130 fs/namei.c:5075 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcf/0x260 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&wnd->rw_lock/1){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2478/0x3b30 kernel/locking/lockdep.c:5137 lock_acquire kernel/locking/lockdep.c:5754 [inline] lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5719 down_write_nested+0x3d/0x50 kernel/locking/rwsem.c:1695 ntfs_mark_rec_free+0x2f4/0x400 fs/ntfs3/fsntfs.c:742 ni_write_inode+0x4e2/0x2920 fs/ntfs3/frecord.c:3365 write_inode fs/fs-writeback.c:1497 [inline] __writeback_single_inode+0xb39/0xf90 fs/fs-writeback.c:1716 writeback_sb_inodes+0x611/0x1150 fs/fs-writeback.c:1947 wb_writeback+0x199/0xb50 fs/fs-writeback.c:2127 wb_do_writeback fs/fs-writeback.c:2274 [inline] wb_workfn+0x28d/0xf40 fs/fs-writeback.c:2314 process_one_work+0x9fe/0x1b60 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xf70 kernel/workqueue.c:3393 kthread+0x2c4/0x3a0 kernel/kthread.c:389 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->ni_lock#3); lock(&wnd->rw_lock/1); lock(&ni->ni_lock#3); lock(&wnd->rw_lock/1); *** DEADLOCK *** 3 locks held by kworker/u8:18/11086: #0: ffff88801b6f4148 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x12bf/0x1b60 kernel/workqueue.c:3206 #1: ffffc90009287d80 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x957/0x1b60 kernel/workqueue.c:3207 #2: ffff88805c7434a0 (&ni->ni_lock#3){+.+.}-{3:3}, at: ni_trylock fs/ntfs3/ntfs_fs.h:1143 [inline] #2: ffff88805c7434a0 (&ni->ni_lock#3){+.+.}-{3:3}, at: ni_write_inode+0x24a/0x2920 fs/ntfs3/frecord.c:3265 stack backtrace: CPU: 1 PID: 11086 Comm: kworker/u8:18 Not tainted 6.9.0-syzkaller-08284-gea5f6ad9ad96 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 Workqueue: writeback wb_workfn (flush-7:5) Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:114 check_noncircular+0x31a/0x400 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 kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2478/0x3b30 kernel/locking/lockdep.c:5137 lock_acquire kernel/locking/lockdep.c:5754 [inline] lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5719 down_write_nested+0x3d/0x50 kernel/locking/rwsem.c:1695 ntfs_mark_rec_free+0x2f4/0x400 fs/ntfs3/fsntfs.c:742 ni_write_inode+0x4e2/0x2920 fs/ntfs3/frecord.c:3365 write_inode fs/fs-writeback.c:1497 [inline] __writeback_single_inode+0xb39/0xf90 fs/fs-writeback.c:1716 writeback_sb_inodes+0x611/0x1150 fs/fs-writeback.c:1947 wb_writeback+0x199/0xb50 fs/fs-writeback.c:2127 wb_do_writeback fs/fs-writeback.c:2274 [inline] wb_workfn+0x28d/0xf40 fs/fs-writeback.c:2314 process_one_work+0x9fe/0x1b60 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xf70 kernel/workqueue.c:3393 kthread+0x2c4/0x3a0 kernel/kthread.c:389 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244