[v5.15] INFO: rcu detected stall in el1h_64_irq (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3dea0e7f549e Linux 5.15.186
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11d4c770580000
kernel config: https://syzkaller.appspot.com/x/.config?x=68f6f35276e57732
dashboard link: https://syzkaller.appspot.com/bug?extid=c203fd674bd766512a9f
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/90580e8155e1/disk-3dea0e7f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fa25a3db336a/vmlinux-3dea0e7f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0b05b2d29242/Image-3dea0e7f.gz.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
(detected by 0, t=10502 jiffies, g=31005, q=43)
rcu: All QSes seen, last rcu_preempt kthread activity 10502 (4295002602-4294992100), jiffies_till_next_fqs=1, root ->qsmask 0x0
rcu: rcu_preempt kthread starved for 10502 jiffies! g31005 f0x0 RCU_GP_DONE_GPS(2) ->state=0x0 ->cpu=0
rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt state:R running task stack: 0 pid: 15 ppid: 2 flags:0x00000008
Call trace:
__switch_to+0x2f4/0x558 arch/arm64/kernel/process.c:521
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xe00/0x1c0c kernel/sched/core.c:6376
preempt_schedule_common+0x138/0x218 kernel/sched/core.c:6552
preempt_schedule+0x64/0x84 kernel/sched/core.c:6577
__raw_spin_unlock_irq include/linux/spinlock_api_smp.h:169 [inline]
_raw_spin_unlock_irq+0xe4/0x128 kernel/locking/spinlock.c:202
rcu_gp_init+0x384/0x17f0 kernel/rcu/tree.c:1772
rcu_gp_kthread+0x150/0x2a8 kernel/rcu/tree.c:2135
kthread+0x374/0x454 kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:855
rcu: Stack dump where RCU GP kthread last ran:
Task dump for CPU 0:
task:syz.2.1822 state:R running task stack: 0 pid:10075 ppid: 4032 flags:0x00000001
Call trace:
dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
sched_show_task+0x3c8/0x4b4 kernel/sched/core.c:8640
dump_cpu_task+0x84/0xa8 kernel/sched/core.c:10927
rcu_check_gp_kthread_starvation+0x1e8/0x274 kernel/rcu/tree_stall.h:488
print_other_cpu_stall+0x1a24/0x1c10 kernel/rcu/tree_stall.h:592
check_cpu_stall kernel/rcu/tree_stall.h:745 [inline]
rcu_pending kernel/rcu/tree.c:3932 [inline]
rcu_sched_clock_irq+0x1558/0x1810 kernel/rcu/tree.c:2619
update_process_times+0x1c4/0x260 kernel/time/timer.c:1818
tick_sched_handle kernel/time/tick-sched.c:254 [inline]
tick_sched_timer+0x30c/0x4bc kernel/time/tick-sched.c:1473
__run_hrtimer kernel/time/hrtimer.c:1690 [inline]
__hrtimer_run_queues+0x3fc/0xb6c kernel/time/hrtimer.c:1754
hrtimer_interrupt+0x2bc/0xb5c kernel/time/hrtimer.c:1816
timer_handler drivers/clocksource/arm_arch_timer.c:659 [inline]
arch_timer_handler_virt+0x74/0x88 drivers/clocksource/arm_arch_timer.c:670
handle_percpu_devid_irq+0x29c/0x76c kernel/irq/chip.c:930
generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
handle_irq_desc kernel/irq/irqdesc.c:652 [inline]
handle_domain_irq+0x144/0x1fc kernel/irq/irqdesc.c:707
gic_handle_irq+0x78/0x1c8 drivers/irqchip/irq-gic-v3.c:765
call_on_irq_stack+0x24/0x30 arch/arm64/kernel/entry.S:855
do_interrupt_handler+0x6c/0x88 arch/arm64/kernel/entry-common.c:267
el1_interrupt+0x30/0x58 arch/arm64/kernel/entry-common.c:454
el1h_64_irq_handler+0x18/0x24 arch/arm64/kernel/entry-common.c:470
el1h_64_irq+0x78/0x7c arch/arm64/kernel/entry.S:522
__sanitizer_cov_trace_pc+0x80/0xac kernel/kcov.c:206
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584


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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

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