INFO: task can't die in sysvec_apic_timer_interrupt

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 15ac8fdb Add linux-next specific files for 20201207
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=124feb9b500000
kernel config: https://syzkaller.appspot.com/x/.config?x=3696b8138207d24d
dashboard link: https://syzkaller.appspot.com/bug?extid=fdb21f79d53b2c025855
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [b...@alien8.de dw...@amazon.co.uk h...@zytor.com linux-...@vger.kernel.org lu...@kernel.org mi...@redhat.com tg...@linutronix.de x...@kernel.org]

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

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

INFO: task syz-executor.5:11026 can't die for more than 143 seconds.
task:syz-executor.5 state:R running task stack:25952 pid:11026 ppid: 8509 flags:0x00004006
Call Trace:
context_switch kernel/sched/core.c:4325 [inline]
__schedule+0x8eb/0x21b0 kernel/sched/core.c:5076
sysvec_apic_timer_interrupt+0x4d/0x100 arch/x86/kernel/apic/apic.c:1096
INFO: task syz-executor.4:11019 can't die for more than 146 seconds.
task:syz-executor.4 state:R running task stack:25768 pid:11019 ppid: 8478 flags:0x00004006
Call Trace:
context_switch kernel/sched/core.c:4325 [inline]
__schedule+0x8eb/0x21b0 kernel/sched/core.c:5076
INFO: task syz-executor.0:11038 can't die for more than 148 seconds.
task:syz-executor.0 state:R running task stack:26968 pid:11038 ppid: 8470 flags:0x00004006
Call Trace:
INFO: task syz-executor.2:11044 can't die for more than 149 seconds.
task:syz-executor.2 state:R running task stack:25880 pid:11044 ppid: 8474 flags:0x00004006
Call Trace:

Showing all locks held in the system:
3 locks held by kworker/u4:1/22:
1 lock held by khungtaskd/1663:
#0: ffffffff8b78db60 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x28c kernel/locking/lockdep.c:6254
1 lock held by in:imklog/8153:
#0: ffff88801454dc70 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0xe9/0x100 fs/file.c:923
2 locks held by agetty/8156:
#0: ffff888021574098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:266
#1: ffffc90000f092e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x21d/0x1ac0 drivers/tty/n_tty.c:2158
2 locks held by kworker/0:5/9777:
#0: ffff8880b9c34fd8 (&rq->lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1318 [inline]
#0: ffff8880b9c34fd8 (&rq->lock){-.-.}-{2:2}, at: __schedule+0x235/0x21b0 kernel/sched/core.c:4993
#1: ffff8880b9c20088 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x305/0x440 kernel/sched/psi.c:833
1 lock held by syz-executor.5/11026:
1 lock held by syz-executor.4/11019:
3 locks held by syz-executor.2/11044:

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



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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.