syzbot


INFO: task can't die in isolate_lru_pages

Status: auto-closed as invalid on 2022/03/18 23:04
Subsystems: mm
[Documentation on labels]
Reported-by: syzbot+4404578da12e16e8a77e@syzkaller.appspotmail.com
First crash: 827d, last: 827d

Sample crash report:
INFO: task syz-executor.0:27685 can't die for more than 143 seconds.
task:syz-executor.0  state:R  running task     stack:24528 pid:27685 ppid:  5131 flags:0x00004006
Call Trace:
 <TASK>
 isolate_lru_pages+0x32d/0x1b00 mm/vmscan.c:2139
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/26:
 #0: ffffffff8bb83520 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x260 kernel/locking/lockdep.c:6460
2 locks held by getty/3278:
 #0: ffff88814acdc098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:244
 #1: ffffc90002b632e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xcf0/0x1230 drivers/tty/n_tty.c:2077
2 locks held by kworker/u4:24/11760:
1 lock held by syz-executor.0/27685:

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

Kernel panic - not syncing: hung_task: blocked tasks
CPU: 1 PID: 26 Comm: khungtaskd Not tainted 5.16.0-next-20220117-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 panic+0x2b0/0x605 kernel/panic.c:237
 check_hung_uninterruptible_tasks kernel/hung_task.c:260 [inline]
 watchdog.cold+0x1ca/0x1de kernel/hung_task.c:413
 kthread+0x2e9/0x3a0 kernel/kthread.c:377
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/01/17 23:03 linux-next 68e0667e38d9 731a2d23 .config console log report info ci-upstream-linux-next-kasan-gce-root INFO: task can't die in isolate_lru_pages
* Struck through repros no longer work on HEAD.