INFO: task can't die in trace_hardirqs_on

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6f59bc242877 Add linux-next specific files for 20220118
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10c4f67bb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=94e8da4df9ab6319
dashboard link: https://syzkaller.appspot.com/bug?extid=d61cc981618fe8bf95de
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org mi...@redhat.com ros...@goodmis.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+d61cc9...@syzkaller.appspotmail.com

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:

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



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