[v5.15] INFO: task hung in ntfs_readpage

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9e43368a3393 Linux 5.15.129
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1173f59fa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d6b15bee86becf8c
dashboard link: https://syzkaller.appspot.com/bug?extid=dda19c3b6ac9d50b562f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c33277a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11f6912fa80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1286198e60b0/disk-9e43368a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0cc292aa1ff1/vmlinux-9e43368a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d2144049ee33/Image-9e43368a.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/342cfb64c6f5/mount_0.gz

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

INFO: task syz-executor854:5943 blocked for more than 143 seconds.
Not tainted 5.15.129-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor854 state:D stack: 0 pid: 5943 ppid: 4030 flags:0x0000000d
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
ni_lock fs/ntfs3/ntfs_fs.h:1110 [inline]
ntfs_readpage+0x140/0x1c0 fs/ntfs3/inode.c:724
filemap_read_page+0x150/0x454 mm/filemap.c:2386
filemap_fault+0xac4/0xf5c mm/filemap.c:3165
__do_fault+0x120/0x5d0 mm/memory.c:3898
do_read_fault mm/memory.c:4234 [inline]
do_fault mm/memory.c:4362 [inline]
handle_pte_fault mm/memory.c:4621 [inline]
__handle_mm_fault mm/memory.c:4756 [inline]
handle_mm_fault+0x21ec/0x33c4 mm/memory.c:4854
__do_page_fault arch/arm64/mm/fault.c:505 [inline]
do_page_fault+0x700/0xb60 arch/arm64/mm/fault.c:605
do_translation_fault+0xe8/0x138 arch/arm64/mm/fault.c:686
do_mem_abort+0x70/0x1d8 arch/arm64/mm/fault.c:819
el0_da+0x94/0x20c arch/arm64/kernel/entry-common.c:482
el0t_64_sync_handler+0xc0/0xe4 arch/arm64/kernel/entry-common.c:617
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor854:5954 blocked for more than 143 seconds.
Not tainted 5.15.129-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor854 state:D stack: 0 pid: 5954 ppid: 4030 flags:0x0000000d
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
io_schedule+0x8c/0x194 kernel/sched/core.c:8480
wait_on_page_bit_common+0x6fc/0xc14 mm/filemap.c:1356
__lock_page mm/filemap.c:1648 [inline]
lock_page include/linux/pagemap.h:625 [inline]
pagecache_get_page+0x66c/0xd94 mm/filemap.c:1910
find_or_create_page include/linux/pagemap.h:420 [inline]
ni_readpage_cmpr+0x29c/0x68c fs/ntfs3/frecord.c:2087
ntfs_readpage+0x14c/0x1c0 fs/ntfs3/inode.c:725
filemap_read_page+0x150/0x454 mm/filemap.c:2386
filemap_fault+0xac4/0xf5c mm/filemap.c:3165
__do_fault+0x120/0x5d0 mm/memory.c:3898
do_read_fault mm/memory.c:4234 [inline]
do_fault mm/memory.c:4362 [inline]
handle_pte_fault mm/memory.c:4621 [inline]
__handle_mm_fault mm/memory.c:4756 [inline]
handle_mm_fault+0x21ec/0x33c4 mm/memory.c:4854
__do_page_fault arch/arm64/mm/fault.c:505 [inline]
do_page_fault+0x700/0xb60 arch/arm64/mm/fault.c:605
do_translation_fault+0xe8/0x138 arch/arm64/mm/fault.c:686
do_mem_abort+0x70/0x1d8 arch/arm64/mm/fault.c:819
el1_abort+0x3c/0x5c arch/arm64/kernel/entry-common.c:358
el1h_64_sync_handler+0x5c/0x98 arch/arm64/kernel/entry-common.c:409
el1h_64_sync+0x78/0x7c arch/arm64/kernel/entry.S:579
__arch_copy_from_user+0xa4/0x218 arch/arm64/lib/copy_template.S:94
__sys_bpf+0x1b8/0x610 kernel/bpf/syscall.c:4587
__do_sys_bpf kernel/bpf/syscall.c:4718 [inline]
__se_sys_bpf kernel/bpf/syscall.c:4716 [inline]
__arm64_sys_bpf+0x80/0x98 kernel/bpf/syscall.c:4716
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffff800014ad1a20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3721:
#0:
ffff0000d2d4b098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff800018de02e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1204 drivers/tty/n_tty.c:2158
2 locks held by udevd/4044:
2 locks held by udevd/4129:
#0: ffff0000cb725918 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xe0/0x6b0 block/bdev.c:912
#1: ffff0000cb71a468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa8/0x9b8 drivers/block/loop.c:1365
1 lock held by udevd/5646:
2 locks held by syz-executor854/5943:
#0: ffff0000df0a5660 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:842 [inline]
#0: ffff0000df0a5660 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_fault+0x52c/0xf5c mm/filemap.c:3072
#1: ffff0000df0a5220 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1110 [inline]
#1: ffff0000df0a5220 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_readpage+0x140/0x1c0 fs/ntfs3/inode.c:724
2 locks held by syz-executor854/5954:
#0: ffff0000df0a5660 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:842 [inline]
#0: ffff0000df0a5660 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_fault+0x71c/0xf5c mm/filemap.c:3087
#1: ffff0000df0a5220 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1110 [inline]
#1: ffff0000df0a5220 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_readpage+0x140/0x1c0 fs/ntfs3/inode.c:724
2 locks held by syz-executor854/14283:
2 locks held by syz-executor854/14285:
2 locks held by syz-executor854/14287:

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



---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite 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