=====================================================
WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
5.19.0-rc3-syzkaller-00043-g3abc3ae553c7 #0 Not tainted
-----------------------------------------------------
syz-executor298/3612 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
ffffffff8c80a058 (tasklist_lock){.+.+}-{2:2}, at: send_sigio+0xbe/0x300 fs/fcntl.c:791

and this task is already holding:
ffff888021360130 (&f->f_owner.lock){....}-{2:2}, at: send_sigio+0x2f/0x300 fs/fcntl.c:777
which would create a new lock dependency:
 (&f->f_owner.lock){....}-{2:2} -> (tasklist_lock){.+.+}-{2:2}

but this new dependency connects a HARDIRQ-irq-safe lock:
 (&timer->lock){-...}-{2:2}