[v5.15] INFO: rcu detected stall in __run_timers

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4fdad925aa1a Linux 5.15.107
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=173bee4fc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d9bc1b227ee6c412
dashboard link: https://syzkaller.appspot.com/bug?extid=0e682c4891716c50038d
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6a7f3b0f6a27/disk-4fdad925.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/db34418039b7/vmlinux-4fdad925.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4e96525a950a/bzImage-4fdad925.xz

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

rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 1-....: (10449 ticks this GP) idle=025/1/0x4000000000000000 softirq=132731/132731 fqs=2054
(t=10501 jiffies g=240797 q=5383)
NMI backtrace for cpu 1
CPU: 1 PID: 1065 Comm: kworker/1:2 Not tainted 5.15.107-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
Workqueue: events nsim_dev_trap_report_work
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_single_cpu_backtrace include/linux/nmi.h:166 [inline]
rcu_dump_cpu_stacks+0x223/0x390 kernel/rcu/tree_stall.h:343
print_cpu_stall kernel/rcu/tree_stall.h:627 [inline]
check_cpu_stall kernel/rcu/tree_stall.h:711 [inline]
rcu_pending kernel/rcu/tree.c:3887 [inline]
rcu_sched_clock_irq+0xf26/0x1770 kernel/rcu/tree.c:2605
update_process_times+0x196/0x200 kernel/time/timer.c:1788
tick_sched_handle kernel/time/tick-sched.c:226 [inline]
tick_sched_timer+0x22d/0x3c0 kernel/time/tick-sched.c:1420
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x55b/0xcf0 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1086 [inline]
__sysvec_apic_timer_interrupt+0x139/0x470 arch/x86/kernel/apic/apic.c:1103
sysvec_apic_timer_interrupt+0x3e/0xb0 arch/x86/kernel/apic/apic.c:1097
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:__raw_spin_unlock_irq include/linux/spinlock_api_smp.h:169 [inline]
RIP: 0010:_raw_spin_unlock_irq+0x25/0x40 kernel/locking/spinlock.c:202
Code: c1 aa f6 ff 90 53 48 89 fb 48 83 c7 18 48 8b 74 24 08 e8 be 00 42 f7 48 89 df e8 56 53 43 f7 e8 91 cd 65 f7 fb bf 01 00 00 00 <e8> e6 93 36 f7 65 8b 05 07 13 e2 75 85 c0 74 02 5b c3 e8 14 2a e0
RSP: 0018:ffffc90000dd0d50 EFLAGS: 00000282
RAX: 2e54316b1e421800 RBX: ffff8880b9b28080 RCX: ffffffff8162a4d8
RDX: dffffc0000000000 RSI: ffffffff8a8af0e0 RDI: 0000000000000001
RBP: ffffc90000dd0eb0 R08: dffffc0000000000 R09: fffffbfff1f76e33
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880ab5d3010
R13: 1ffff11017365018 R14: ffff8880ab5d3030 R15: ffffffff884d3ac0
expire_timers kernel/time/timer.c:1465 [inline]
__run_timers+0x66c/0x890 kernel/time/timer.c:1737
run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1750
__do_softirq+0x3b3/0x93a kernel/softirq.c:558
do_softirq+0x162/0x240 kernel/softirq.c:459
</IRQ>
<TASK>
__local_bh_enable_ip+0x1b1/0x1f0 kernel/softirq.c:383
spin_unlock_bh include/linux/spinlock.h:408 [inline]
nsim_dev_trap_report drivers/net/netdevsim/dev.c:739 [inline]
nsim_dev_trap_report_work+0x780/0xab0 drivers/net/netdevsim/dev.c:765
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>


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