BUG: soft lockup in __run_timers

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ca72d58361ee Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=175e4cbb480000
kernel config: https://syzkaller.appspot.com/x/.config?x=c393c46b4d99bd44
dashboard link: https://syzkaller.appspot.com/bug?extid=89e77dc58c734e327c44
compiler: Debian clang version 13.0.1-6~deb11u1, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org long...@huawei.com tg...@linutronix.de ubi...@gmail.com vsch...@redhat.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c61dbbcb24f1/disk-ca72d583.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e8bbfee7730b/vmlinux-ca72d583.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d63117edadbc/Image-ca72d583.gz.xz

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

watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ksoftirqd/0:14]
Modules linked in:
irq event stamp: 49149847
hardirqs last enabled at (49149846): [<ffff80000c13db94>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline]
hardirqs last enabled at (49149846): [<ffff80000c13db94>] _raw_spin_unlock_irq+0x3c/0x6c kernel/locking/spinlock.c:202
hardirqs last disabled at (49149847): [<ffff80000c12aa78>] __el1_irq arch/arm64/kernel/entry-common.c:468 [inline]
hardirqs last disabled at (49149847): [<ffff80000c12aa78>] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:486
softirqs last enabled at (39945482): [<ffff8000080102c4>] _stext+0x2c4/0x34c
softirqs last disabled at (39945511): [<ffff80000810dfd8>] run_ksoftirqd+0x40/0x108 kernel/softirq.c:934
CPU: 0 PID: 14 Comm: ksoftirqd/0 Not tainted 6.2.0-rc6-syzkaller-17549-gca72d58361ee #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:160 [inline]
pc : _raw_spin_unlock_irq+0x40/0x6c kernel/locking/spinlock.c:202
lr : __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline]
lr : _raw_spin_unlock_irq+0x3c/0x6c kernel/locking/spinlock.c:202
sp : ffff80000f4abc80
x29: ffff80000f4abc80 x28: dead000000000122 x27: ffff80000f4abcb8
x26: 000000000a400000 x25: 0000000000000000 x24: ffff80000b3d4a58
x23: ffff0001334b8210 x22: 000000010001b8a9 x21: 0000000000000000
x20: ffff80000c1808a0 x19: ffff0001fefc0980 x18: 000000007c11071d
x17: 00000000d92a1f29 x16: ffff80000ddcb118 x15: ffff0000c0319a00
x14: 0000000000000000 x13: 00000000ffffffff x12: ffff0000c0319a00
x11: ff808000095ef9f4 x10: 0000000000000000 x9 : ffff8000095ef9f4
x8 : 0000000002edf796 x7 : ffff8000095f0948 x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000
x2 : ffff80000f4abc18 x1 : ffff80000d089ee7 x0 : ffff8001f1b0c000
Call trace:
__daif_local_irq_enable arch/arm64/include/asm/irqflags.h:33 [inline]
arch_local_irq_enable arch/arm64/include/asm/irqflags.h:55 [inline]
__raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline]
_raw_spin_unlock_irq+0x40/0x6c kernel/locking/spinlock.c:202
expire_timers kernel/time/timer.c:1750 [inline]
__run_timers+0x274/0x384 kernel/time/timer.c:2022
run_timer_softirq+0x34/0x5c kernel/time/timer.c:2035
_stext+0x164/0x34c
run_ksoftirqd+0x40/0x108 kernel/softirq.c:934
smpboot_thread_fn+0x248/0x3ec kernel/smpboot.c:164
kthread+0x12c/0x158 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870


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