====================================================== WARNING: possible circular locking dependency detected 6.2.0-rc2-syzkaller #0 Not tainted ------------------------------------------------------ kworker/u4:10/5907 is trying to acquire lock: ffff88802f434120 (&wnd->rw_lock/1){++++}-{3:3}, at: ntfs_mark_rec_free+0x3b/0x2b0 fs/ntfs3/fsntfs.c:741 but task is already holding lock: ffff888079050100 (&ni->ni_lock){+.+.}-{3:3}, at: ni_trylock fs/ntfs3/ntfs_fs.h:1142 [inline] ffff888079050100 (&ni->ni_lock){+.+.}-{3:3}, at: ni_write_inode+0x14d/0x11e0 fs/ntfs3/frecord.c:3255 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&ni->ni_lock){+.+.}-{3:3}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 __mutex_lock_common+0x1bd/0x26e0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799 ntfs_set_state+0x1da/0x680 fs/ntfs3/fsntfs.c:946 attr_set_size+0x330d/0x4090 fs/ntfs3/attrib.c:867 ntfs_extend_mft+0x2c7/0x470 fs/ntfs3/fsntfs.c:526 ntfs_look_free_mft+0x391/0xf90 fs/ntfs3/fsntfs.c:589 ni_create_attr_list+0x96e/0x1480 fs/ntfs3/frecord.c:873 ni_ins_attr_ext+0x330/0xbc0 fs/ntfs3/frecord.c:968 ni_insert_attr+0x33a/0x920 fs/ntfs3/frecord.c:1135 ni_insert_resident+0xca/0x3b0 fs/ntfs3/frecord.c:1519 ntfs_set_ea+0xbdf/0x1620 fs/ntfs3/xattr.c:432 ntfs_save_wsl_perm+0x137/0x490 fs/ntfs3/xattr.c:962 ntfs3_setattr+0xa90/0xca0 fs/ntfs3/file.c:722 notify_change+0xe50/0x1100 fs/attr.c:482 chown_common+0x5b6/0x910 fs/open.c:736 do_fchownat+0x165/0x240 fs/open.c:767 __do_sys_fchownat fs/open.c:782 [inline] __se_sys_fchownat fs/open.c:779 [inline] __x64_sys_fchownat+0xb1/0xc0 fs/open.c:779 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #1 (&ni->file.run_lock#2){++++}-{3:3}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 down_write+0x9c/0x270 kernel/locking/rwsem.c:1562 ntfs_extend_mft+0x12d/0x470 fs/ntfs3/fsntfs.c:510 ntfs_look_free_mft+0x391/0xf90 fs/ntfs3/fsntfs.c:589 ntfs_create_inode+0x4a5/0x3560 fs/ntfs3/inode.c:1299 ntfs_atomic_open+0x3e3/0x540 fs/ntfs3/namei.c:424 atomic_open fs/namei.c:3276 [inline] lookup_open fs/namei.c:3384 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0xf15/0x2dd0 fs/namei.c:3711 do_filp_open+0x264/0x4f0 fs/namei.c:3741 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_open fs/open.c:1334 [inline] __se_sys_open fs/open.c:1330 [inline] __x64_sys_open+0x221/0x270 fs/open.c:1330 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 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:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain+0x1898/0x6ae0 kernel/locking/lockdep.c:3831 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 down_write_nested+0xa2/0x280 kernel/locking/rwsem.c:1672 ntfs_mark_rec_free+0x3b/0x2b0 fs/ntfs3/fsntfs.c:741 ni_write_inode+0x41a/0x11e0 fs/ntfs3/frecord.c:3348 write_inode fs/fs-writeback.c:1451 [inline] __writeback_single_inode+0x4d6/0x670 fs/fs-writeback.c:1663 writeback_sb_inodes+0x812/0x1050 fs/fs-writeback.c:1889 wb_writeback+0x41f/0x7b0 fs/fs-writeback.c:2063 wb_do_writeback fs/fs-writeback.c:2206 [inline] wb_workfn+0x3cb/0xef0 fs/fs-writeback.c:2246 process_one_work+0x877/0xdb0 kernel/workqueue.c:2289 worker_thread+0xb14/0x1330 kernel/workqueue.c:2436 kthread+0x266/0x300 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 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:10/5907: #0: ffff888017dc4938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7f2/0xdb0 #1: ffffc9000ba57d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x831/0xdb0 kernel/workqueue.c:2264 #2: ffff888079050100 (&ni->ni_lock){+.+.}-{3:3}, at: ni_trylock fs/ntfs3/ntfs_fs.h:1142 [inline] #2: ffff888079050100 (&ni->ni_lock){+.+.}-{3:3}, at: ni_write_inode+0x14d/0x11e0 fs/ntfs3/frecord.c:3255 stack backtrace: CPU: 1 PID: 5907 Comm: kworker/u4:10 Not tainted 6.2.0-rc2-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Workqueue: writeback wb_workfn (flush-7:1) Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x290 lib/dump_stack.c:106 check_noncircular+0x2cc/0x390 kernel/locking/lockdep.c:2177 check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain+0x1898/0x6ae0 kernel/locking/lockdep.c:3831 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 down_write_nested+0xa2/0x280 kernel/locking/rwsem.c:1672 ntfs_mark_rec_free+0x3b/0x2b0 fs/ntfs3/fsntfs.c:741 ni_write_inode+0x41a/0x11e0 fs/ntfs3/frecord.c:3348 write_inode fs/fs-writeback.c:1451 [inline] __writeback_single_inode+0x4d6/0x670 fs/fs-writeback.c:1663 writeback_sb_inodes+0x812/0x1050 fs/fs-writeback.c:1889 wb_writeback+0x41f/0x7b0 fs/fs-writeback.c:2063 wb_do_writeback fs/fs-writeback.c:2206 [inline] wb_workfn+0x3cb/0xef0 fs/fs-writeback.c:2246 process_one_work+0x877/0xdb0 kernel/workqueue.c:2289 worker_thread+0xb14/0x1330 kernel/workqueue.c:2436 kthread+0x266/0x300 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308