======================================================
WARNING: possible circular locking dependency detected
6.5.0-rc7-syzkaller-00164-g382d4cd18475 #0 Not tainted
------------------------------------------------------
kworker/u4:14/14867 is trying to acquire lock:
ffff8880296c4120 (&wnd->rw_lock/1){+.+.}-{3:3}, at: ntfs_mark_rec_free+0x3f/0x2b0 fs/ntfs3/fsntfs.c:742
but task is already holding lock:
ffff88803cff9e80 (&ni->ni_lock){+.+.}-{3:3}, at: ni_trylock fs/ntfs3/ntfs_fs.h:1144 [inline]
ffff88803cff9e80 (&ni->ni_lock){+.+.}-{3:3}, at: ni_write_inode+0x167/0x10a0 fs/ntfs3/frecord.c:3256
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (&ni->ni_lock){+.+.}-{3:3}:
__mutex_lock_common+0x1d8/0x2530 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
ntfs_set_state+0x212/0x730 fs/ntfs3/fsntfs.c:946
attr_set_size+0x3311/0x4290 fs/ntfs3/attrib.c:866
ntfs_extend_mft+0x2fa/0x4b0 fs/ntfs3/fsntfs.c:527
ntfs_look_free_mft+0x43d/0x10c0 fs/ntfs3/fsntfs.c:590
ni_create_attr_list+0x9bd/0x1480 fs/ntfs3/frecord.c:876
ni_ins_attr_ext+0x365/0xbe0 fs/ntfs3/frecord.c:974
ni_insert_attr+0x358/0x900 fs/ntfs3/frecord.c:1141
ni_insert_resident+0xf8/0x3c0 fs/ntfs3/frecord.c:1525
ntfs_set_ea+0xabc/0x16c0 fs/ntfs3/xattr.c:437
ntfs_save_wsl_perm+0x14f/0x500 fs/ntfs3/xattr.c:946
ntfs3_setattr+0x933/0xb00 fs/ntfs3/file.c:708
notify_change+0xc8b/0xf40 fs/attr.c:483
chown_common+0x500/0x850 fs/open.c:768
do_fchownat+0x16d/0x240 fs/open.c:799
__do_sys_chown fs/open.c:819 [inline]
__se_sys_chown fs/open.c:817 [inline]
__x64_sys_chown+0x82/0x90 fs/open.c:817
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #1 (&ni->file.run_lock#2){++++}-{3:3}:
down_write+0x3a/0x50 kernel/locking/rwsem.c:1573
ntfs_extend_mft+0x160/0x4b0 fs/ntfs3/fsntfs.c:511
ntfs_look_free_mft+0x43d/0x10c0 fs/ntfs3/fsntfs.c:590
ni_create_attr_list+0x9bd/0x1480 fs/ntfs3/frecord.c:876
ni_ins_attr_ext+0x365/0xbe0 fs/ntfs3/frecord.c:974
ni_insert_attr+0x358/0x900 fs/ntfs3/frecord.c:1141
ni_insert_resident+0xf8/0x3c0 fs/ntfs3/frecord.c:1525
ntfs_set_ea+0xabc/0x16c0 fs/ntfs3/xattr.c:437
ntfs_save_wsl_perm+0x14f/0x500 fs/ntfs3/xattr.c:946
ntfs3_setattr+0x933/0xb00 fs/ntfs3/file.c:708
notify_change+0xc8b/0xf40 fs/attr.c:483
chown_common+0x500/0x850 fs/open.c:768
do_fchownat+0x16d/0x240 fs/open.c:799
__do_sys_chown fs/open.c:819 [inline]
__se_sys_chown fs/open.c:817 [inline]
__x64_sys_chown+0x82/0x90 fs/open.c:817
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #0 (&wnd->rw_lock/1){+.+.}-{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+0x39ff/0x7f70 kernel/locking/lockdep.c:5144
lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5761
down_write_nested+0x3d/0x50 kernel/locking/rwsem.c:1689
ntfs_mark_rec_free+0x3f/0x2b0 fs/ntfs3/fsntfs.c:742
ni_write_inode+0x516/0x10a0 fs/ntfs3/frecord.c:3352
write_inode fs/fs-writeback.c:1456 [inline]
__writeback_single_inode+0x69b/0xfa0 fs/fs-writeback.c:1668
writeback_sb_inodes+0x8e3/0x11d0 fs/fs-writeback.c:1894
wb_writeback+0x44d/0xc60 fs/fs-writeback.c:2070
wb_do_writeback fs/fs-writeback.c:2217 [inline]
wb_workfn+0x400/0xff0 fs/fs-writeback.c:2257
process_one_work+0x92c/0x12c0 kernel/workqueue.c:2600
worker_thread+0xa63/0x1210 kernel/workqueue.c:2751
kthread+0x2b8/0x350 kernel/kthread.c:389
ret_from_fork+0x2e/0x60 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:
Chain exists of:
&wnd->rw_lock/1 --> &ni->file.run_lock#2 --> &ni->ni_lock
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&ni->ni_lock);
lock(&ni->file.run_lock#2);
lock(&ni->ni_lock);
lock(&wnd->rw_lock/1);
*** DEADLOCK ***
3 locks held by kworker/u4:14/14867:
#0: ffff88814364e138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7e3/0x12c0 kernel/workqueue.c:2572
#1: ffffc90005e27d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x82b/0x12c0 kernel/workqueue.c:2574
#2: ffff88803cff9e80 (&ni->ni_lock){+.+.}-{3:3}, at: ni_trylock fs/ntfs3/ntfs_fs.h:1144 [inline]
#2: ffff88803cff9e80 (&ni->ni_lock){+.+.}-{3:3}, at: ni_write_inode+0x167/0x10a0 fs/ntfs3/frecord.c:3256
stack backtrace:
CPU: 0 PID: 14867 Comm: kworker/u4:14 Not tainted 6.5.0-rc7-syzkaller-00164-g382d4cd18475 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue: writeback wb_workfn (flush-7:1)
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
check_noncircular+0x375/0x4a0 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+0x39ff/0x7f70 kernel/locking/lockdep.c:5144
lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5761
down_write_nested+0x3d/0x50 kernel/locking/rwsem.c:1689
ntfs_mark_rec_free+0x3f/0x2b0 fs/ntfs3/fsntfs.c:742
ni_write_inode+0x516/0x10a0 fs/ntfs3/frecord.c:3352
write_inode fs/fs-writeback.c:1456 [inline]
__writeback_single_inode+0x69b/0xfa0 fs/fs-writeback.c:1668
writeback_sb_inodes+0x8e3/0x11d0 fs/fs-writeback.c:1894
wb_writeback+0x44d/0xc60 fs/fs-writeback.c:2070
wb_do_writeback fs/fs-writeback.c:2217 [inline]
wb_workfn+0x400/0xff0 fs/fs-writeback.c:2257
process_one_work+0x92c/0x12c0 kernel/workqueue.c:2600
worker_thread+0xa63/0x1210 kernel/workqueue.c:2751
kthread+0x2b8/0x350 kernel/kthread.c:389
ret_from_fork+0x2e/0x60 arch/x86/kernel/process.c:145
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
</TASK>