[v6.1] INFO: task hung in ntfs_fallocate

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d2a6dc4eaf6d Linux 6.1.42
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15c14c61a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=bbaa475c49d40952
dashboard link: https://syzkaller.appspot.com/bug?extid=22999e842ba9785ee371
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5046cbfd4e3d/disk-d2a6dc4e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9e953a9099bb/vmlinux-d2a6dc4e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/08c03ca8b9e3/Image-d2a6dc4e.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+22999e...@syzkaller.appspotmail.com

INFO: task syz-executor.3:5669 blocked for more than 145 seconds.
Not tainted 6.1.42-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack:0 pid:5669 ppid:4268 flags:0x00000005
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6554
schedule+0xc4/0x170 kernel/sched/core.c:6630
rwsem_down_write_slowpath+0xc80/0x156c kernel/locking/rwsem.c:1189
__down_write_common kernel/locking/rwsem.c:1314 [inline]
__down_write kernel/locking/rwsem.c:1323 [inline]
down_write+0x84/0x88 kernel/locking/rwsem.c:1574
inode_lock include/linux/fs.h:756 [inline]
ntfs_fallocate+0x25c/0xd88 fs/ntfs3/file.c:569
vfs_fallocate+0x478/0x5b4 fs/open.c:323
ksys_fallocate fs/open.c:346 [inline]
__do_sys_fallocate fs/open.c:354 [inline]
__se_sys_fallocate fs/open.c:352 [inline]
__arm64_sys_fallocate+0xc0/0x110 fs/open.c:352
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581

Showing all locks held in the system:
2 locks held by kworker/u4:1/11:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015a74ef0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffff800015a756f0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffff800015a74d20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
2 locks held by kworker/u4:2/39:
#0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001b307c20 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
2 locks held by kworker/u4:4/264:
#0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001dcb7c20 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
2 locks held by getty/3982:
#0: ffff0000d6201098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bd102f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1210 drivers/tty/n_tty.c:2177
2 locks held by syz-executor.0/4254:
1 lock held by syz-executor.1/4255:
2 locks held by kworker/u4:11/4530:
#0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001de37c20 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
2 locks held by kworker/u4:15/4618:
#0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001e987c20 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
4 locks held by syz-executor.3/5655:
2 locks held by syz-executor.3/5669:
#0: ffff0000d917a460 (sb_writers#22){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2950 [inline]
#0: ffff0000d917a460 (sb_writers#22){.+.+}-{0:0}, at: vfs_fallocate+0x404/0x5b4 fs/open.c:322
#1: ffff00012030f240 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
#1: ffff00012030f240 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: ntfs_fallocate+0x25c/0xd88 fs/ntfs3/file.c:569
1 lock held by udevd/5697:
#0: ffff0000c05455d8 (mapping.invalidate_lock#2){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
#0: ffff0000c05455d8 (mapping.invalidate_lock#2){.+.+}-{3:3}, at: page_cache_ra_unbounded+0xc8/0x58c mm/readahead.c:226
1 lock held by syz-executor.3/7863:
1 lock held by syz-executor.1/7865:
1 lock held by syz-executor.2/7875:
#0: ffff0000c61d8d18 (&rp->fetch_lock){+.+.}-{3:3}, at: mon_bin_fetch+0x48/0x3a4 drivers/usb/mon/mon_bin.c:909
1 lock held by syz-executor.2/7879:
#0: ffff0000d1e98190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
#0: ffff0000d1e98190 (&dev->mutex){....}-{3:3}, at: usbdev_open+0x13c/0x6c0 drivers/usb/core/devio.c:1052

=============================================



---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.