syzbot


INFO: task can't die in trace_hardirqs_on
Status: auto-closed as invalid on 2022/03/19 19:45
Reported-by: syzbot+d61cc981618fe8bf95de@syzkaller.appspotmail.com
First crash: 130d, last: 130d

Sample crash report:
INFO: task syz-executor.0:16028 can't die for more than 143 seconds.
task:syz-executor.0  state:R  running task     stack:24648 pid:16028 ppid: 14918 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:4986 [inline]
 __schedule+0xab2/0x4e90 kernel/sched/core.c:6296
 trace_hardirqs_on+0x5b/0x1c0 kernel/trace/trace_preemptirq.c:49
 xa_entry include/linux/xarray.h:1182 [inline]
 xas_descend+0x2a5/0x3b0 lib/xarray.c:204
 xas_load+0xe5/0x140 lib/xarray.c:240
 </TASK>
INFO: task syz-executor.0:16029 can't die for more than 143 seconds.
task:syz-executor.0  state:R  running task     stack:24760 pid:16029 ppid: 14918 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:4986 [inline]
 __schedule+0xab2/0x4e90 kernel/sched/core.c:6296
 </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/3286:
 #0: ffff88814abc6098 (&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
1 lock held by syz-executor.0/16028:
1 lock held by syz-executor.0/16029:

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


Crashes (1):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-linux-next-kasan-gce-root 2022/01/18 19:44 linux-next 6f59bc242877 731a2d23 .config log report info INFO: task can't die in trace_hardirqs_on