[v6.1] INFO: task hung in truncate_inode_pages

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 88690811da69 Linux 6.1.92
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11f7abe0980000
kernel config: https://syzkaller.appspot.com/x/.config?x=f084fbeeff2de042
dashboard link: https://syzkaller.appspot.com/bug?extid=97853ba2a7926422db1a
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/9040ec940045/disk-88690811.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dc70128611fd/vmlinux-88690811.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f05abc0b618b/Image-88690811.gz.xz

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

INFO: task syz-executor.4:5472 blocked for more than 143 seconds.
Not tainted 6.1.92-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:0 pid:5472 ppid:4253 flags:0x0000000c
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
io_schedule+0x8c/0x188 kernel/sched/core.c:8786
folio_wait_bit_common+0x65c/0xb90 mm/filemap.c:1296
__folio_lock mm/filemap.c:1659 [inline]
folio_lock include/linux/pagemap.h:974 [inline]
__filemap_get_folio+0x5ac/0xb6c mm/filemap.c:1931
truncate_inode_pages_range+0x47c/0xf10 mm/truncate.c:377
truncate_inode_pages+0x2c/0x3c mm/truncate.c:451
kill_bdev block/bdev.c:76 [inline]
blkdev_flush_mapping+0x134/0x280 block/bdev.c:664
blkdev_put_whole block/bdev.c:695 [inline]
blkdev_put+0x464/0x6e0 block/bdev.c:955
blkdev_close+0x58/0x94 block/fops.c:514
__fput+0x30c/0x7bc fs/file_table.c:320
____fput+0x20/0x30 fs/file_table.c:348
task_work_run+0x240/0x2f0 kernel/task_work.c:179
exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0x554/0x1a88 kernel/exit.c:869
do_group_exit+0x194/0x22c kernel/exit.c:1019
get_signal+0x14a0/0x158c kernel/signal.c:2862
do_signal arch/arm64/kernel/signal.c:1076 [inline]
do_notify_resume+0x3ac/0x3474 arch/arm64/kernel/signal.c:1129
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_svc+0x9c/0x168 arch/arm64/kernel/entry-common.c:638
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015a24e70 (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: ffff800015a25670 (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: ffff800015a24ca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
2 locks held by getty/3979:
#0: ffff0000d660b098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bcf02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
1 lock held by syz-fuzzer/4231:
4 locks held by kworker/u4:7/4413:
1 lock held by syz-executor.4/5472:
#0: ffff0000cec324c8 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xec/0x6e0 block/bdev.c:913
1 lock held by syz-executor.4/9967:
#0: ffff0000cec324c8 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x12c/0x8ec block/bdev.c:815
1 lock held by syz-executor.1/10161:
1 lock held by syz-executor.1/10168:
#0: ffff0000c2c96f70 (sk_lock-AF_INET){+.+.}-{0:0}, at: do_ip_getsockopt+0x330/0x2168 net/ipv4/ip_sockglue.c:1572
1 lock held by syz-executor.1/10175:
#0: ffff0000c2c96f70 (sk_lock-AF_INET){+.+.}-{0:0}, at: do_tcp_setsockopt+0x344/0x1fd4 net/ipv4/tcp.c:3554
2 locks held by kworker/1:9/10189:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff8000223b7c20 (free_ipc_work){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
3 locks held by kworker/1:10/10190:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001e037c20 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff0000cccd6240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x270/0x32bc drivers/net/netdevsim/fib.c:1489
1 lock held by syz-executor.3/10254:
#0: ffff0000c35d00e0 (&type->s_umount_key#65/1){+.+.}-{3:3}, at: alloc_super+0x1b4/0x824 fs/super.c:228
3 locks held by syz-executor.4/10262:
#0: ffff0000ce2c10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:552 [inline]
#0: ffff0000ce2c10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1d8/0x4a4 net/bluetooth/hci_core.c:2736
#1: ffff0000ce2c0078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x39c/0xf6c net/bluetooth/hci_sync.c:5005
#2: ffff800017f7ee88 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1805 [inline]
#2: ffff800017f7ee88 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xb0/0x27c net/bluetooth/hci_conn.c:2441
1 lock held by syz-executor.0/10265:

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



---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

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