[v5.15] INFO: task hung in xfs_ilock

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c61bd26ae81a Linux 5.15.160
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=111af026980000
kernel config: https://syzkaller.appspot.com/x/.config?x=235f0e81ca937c17
dashboard link: https://syzkaller.appspot.com/bug?extid=6c6fc2e9761ee5fadcce
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d61a97eef8b9/disk-c61bd26a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ab4908b4b59b/vmlinux-c61bd26a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d818fd46802b/bzImage-c61bd26a.xz

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

INFO: task syz-executor.0:3978 blocked for more than 143 seconds.
Not tainted 5.15.160-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:26624 pid: 3978 ppid: 3531 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
rwsem_down_read_slowpath+0x605/0xb40 kernel/locking/rwsem.c:1055
__down_read_common kernel/locking/rwsem.c:1239 [inline]
__down_read kernel/locking/rwsem.c:1252 [inline]
down_read_nested+0x9c/0x2f0 kernel/locking/rwsem.c:1624
xfs_ilock+0x1c0/0x390 fs/xfs/xfs_inode.c:195
__xfs_filemap_fault+0x3ec/0x950 fs/xfs/xfs_file.c:1337
do_page_mkwrite+0x1a9/0x440 mm/memory.c:2892
wp_page_shared+0x179/0x690 mm/memory.c:3229
handle_pte_fault mm/memory.c:4639 [inline]
__handle_mm_fault mm/memory.c:4756 [inline]
handle_mm_fault+0x2a3d/0x5950 mm/memory.c:4854
do_user_addr_fault arch/x86/mm/fault.c:1388 [inline]
handle_page_fault arch/x86/mm/fault.c:1476 [inline]
exc_page_fault+0x271/0x740 arch/x86/mm/fault.c:1532
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:568
RIP: 0033:0x7f02100bda61
RSP: 002b:00007fffa37475e0 EFLAGS: 00010246
RAX: 0000000020000200 RBX: 0000000000000004 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00005555568f0360
RBP: 00007fffa37476d8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 00007fffa3747700
R13: 00007f0210245f8c R14: 0000000000000032 R15: 00007f0210247980
</TASK>

Showin


---
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

[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=1268bfd6980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee57a613e7f5bf6c
dashboard link: https://syzkaller.appspot.com/bug?extid=09a7ddf1ed061bbb2528

compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:

disk image: https://storage.googleapis.com/syzbot-assets/8b45ba80e02a/disk-88690811.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ca769d644800/vmlinux-88690811.xz
kernel image: https://storage.googleapis.com/syzbot-assets/26a1d8aecbf6/bzImage-88690811.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+09a7dd...@syzkaller.appspotmail.com

INFO: task syz-executor.4:4720 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:23176 pid:4720 ppid:3565 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6693
rwsem_down_read_slowpath kernel/locking/rwsem.c:1094 [inline]
__down_read_common kernel/locking/rwsem.c:1261 [inline]
__down_read kernel/locking/rwsem.c:1274 [inline]
down_read_nested+0x703/0xa40 kernel/locking/rwsem.c:1646
xfs_ilock+0x1e6/0x430 fs/xfs/xfs_inode.c:206
__xfs_filemap_fault+0x3fa/0x9e0 fs/xfs/xfs_file.c:1326
do_page_mkwrite+0x1a1/0x5f0 mm/memory.c:2992
wp_page_shared+0x164/0x380 mm/memory.c:3341
handle_pte_fault mm/memory.c:5031 [inline]
__handle_mm_fault mm/memory.c:5155 [inline]
handle_mm_fault+0x2525/0x5340 mm/memory.c:5276
do_user_addr_fault arch/x86/mm/fault.c:1371 [inline]
handle_page_fault arch/x86/mm/fault.c:1462 [inline]
exc_page_fault+0x26f/0x660 arch/x86/mm/fault.c:1518
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7f57fac2ba61
RSP: 002b:00007ffdef7b1d70 EFLAGS: 00010246

RAX: 0000000020000200 RBX: 0000000000000004 RCX: 0000000000000000

RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00005555573c1360
RBP: 00007ffdef7b1e68 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 00007ffdef7b1e90
R13: 00007f57fadb3f8c R14: 0000000000000032 R15: 00007f57fadb5980
</TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8d12ae50 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8d12b650 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
5 locks held by kworker/0:1/14:
1 lock held by khungtaskd/28:
#0: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6494
2 locks held by getty/3301:
#0: ffff88814b705098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1:
ffffc900031262f0
(
&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2188
1 lock held by syz-fuzzer/3555:
5 locks held by kworker/u4:5/3607:
#0: ffff888012616938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1:
ffffc90003f6fd20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffffffff8e28ecd0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf1/0xb60 net/core/net_namespace.c:566
#3: ffffffff8e29b028 (rtnl_mutex){+.+.}-{3:3}, at: ip_tunnel_delete_nets+0xc9/0x330 net/ipv4/ip_tunnel.c:1148
#4: ffffffff8d130278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchro