[v5.15] INFO: task hung in migrate_pages

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d93fa2c78854 Linux 5.15.145
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16075776e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=68cb856f08cf8214
dashboard link: https://syzkaller.appspot.com/bug?extid=ca5cea833eef2d386860
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/2fdac32b009c/disk-d93fa2c7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5c99dfaee802/vmlinux-d93fa2c7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/52e4895d11f6/bzImage-d93fa2c7.xz

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

INFO: task kcompactd0:30 blocked for more than 143 seconds.
Not tainted 5.15.145-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kcompactd0 state:D stack:25376 pid: 30 ppid: 2 flags:0x00004000
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
io_schedule+0x88/0x100 kernel/sched/core.c:8484
wait_on_page_bit_common+0xa13/0x1180 mm/filemap.c:1356
lock_page include/linux/pagemap.h:625 [inline]
__unmap_and_move mm/migrate.c:990 [inline]
unmap_and_move mm/migrate.c:1214 [inline]
migrate_pages+0xbef/0x3470 mm/migrate.c:1491
compact_zone+0x1ddb/0x4330 mm/compaction.c:2424
proactive_compact_node mm/compaction.c:2678 [inline]
kcompactd+0x19a3/0x2910 mm/compaction.c:2988
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>

Showing all locks held in the system:
2 locks held by kworker/u4:0/9:
1 lock held by khungtaskd/27:
#0: ffffffff8c91f220 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3258:
#0: ffff888024b20098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc9000209b2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
1 lock held by syz-executor.3/25245:
1 lock held by syz-executor.4/25622:
#0: ffff88809ff400e0 (&type->s_umount_key#56){++++}-{3:3}, at: iterate_supers+0xac/0x1e0 fs/super.c:703
1 lock held by syz-executor.4/25727:
#0: ffff88809ff400e0 (&type->s_umount_key#56){++++}-{3:3}, at: iterate_supers+0xac/0x1e0 fs/super.c:703

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.145-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 144 Comm: kworker/u4:1 Not tainted 5.15.145-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: phy11 ieee80211_iface_work
RIP: 0010:ieee80211_ibss_rx_queued_mgmt+0x123/0x2af0 net/mac80211/ibss.c:1634
Code: f6 e8 01 1d 7a 00 49 81 c4 88 0e 00 00 4c 89 e0 48 c1 e8 03 48 89 44 24 70 0f b6 04 18 84 c0 0f 85 99 1e 00 00 41 0f b6 1c 24 <31> ff 89 de e8 d4 da d5 f7 85 db 0f 84 fd 00 00 00 41 81 e7 f0 00
RSP: 0018:ffffc900010cf9c0 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000006 RCX: 0000000000000001
RDX: 0000000000000001 RSI: 0000000000000008 RDI: 0000000000000001
RBP: ffffc900010cfbd8 R08: dffffc0000000000 R09: fffff52000219ef5
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88801a51db08
R13: 1ffff11003fa07aa R14: ffff88801fd03d50 R15: 0000000000000080
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c013c37e90 CR3: 00000000236c1000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
ieee80211_iface_process_skb net/mac80211/iface.c:1441 [inline]
ieee80211_iface_work+0x78f/0xcc0 net/mac80211/iface.c:1495
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>


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