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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13bac422580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=33156cbc55e8de58d5a9
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/998e4247f9d0/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4ef4066c91ec/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/922e7b640c48/bzImage-68efe5a6.xz

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

rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 0-....: (1 GPs behind) idle=9ab/1/0x4000000000000000 softirq=103673/103674 fqs=4604
(t=10500 jiffies g=152041 q=1065)
NMI backtrace for cpu 0
CPU: 0 PID: 30024 Comm: syz.6.6004 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
<IRQ>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_single_cpu_backtrace include/linux/nmi.h:166 [inline]
rcu_dump_cpu_stacks+0x22f/0x380 kernel/rcu/tree_stall.h:349
print_cpu_stall+0x31d/0x5f0 kernel/rcu/tree_stall.h:633
check_cpu_stall kernel/rcu/tree_stall.h:727 [inline]
rcu_pending kernel/rcu/tree.c:3936 [inline]
rcu_sched_clock_irq+0x6d8/0x1110 kernel/rcu/tree.c:2619
update_process_times+0x193/0x200 kernel/time/timer.c:1818
tick_sched_handle kernel/time/tick-sched.c:254 [inline]
tick_sched_timer+0x37d/0x560 kernel/time/tick-sched.c:1473
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x4fe/0xc40 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x3bb/0x8d0 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1097 [inline]
__sysvec_apic_timer_interrupt+0x137/0x4a0 arch/x86/kernel/apic/apic.c:1114
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0x4d/0xc0 arch/x86/kernel/apic/apic.c:1108
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:seqcount_lockdep_reader_access+0x17b/0x1c0 include/linux/seqlock.h:106
Code: 00 4d 85 e4 75 16 e8 54 cc 0f 00 eb 15 e8 4d cc 0f 00 e8 88 e7 39 08 4d 85 e4 74 ea e8 3e cc 0f 00 fb 48 c7 04 24 0e 36 e0 45 <4b> c7 04 3e 00 00 00 00 66 43 c7 44 3e 09 00 00 43 c6 44 3e 0b 00
RSP: 0018:ffffc90000007440 EFLAGS: 00000246
RAX: ffffffff8167ffd2 RBX: 0000000000000000 RCX: ffff88804a1d0000
RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900000074f8 R08: dffffc0000000000 R09: fffffbfff1ff5438
R10: fffffbfff1ff5438 R11: 1ffffffff1ff5437 R12: 0000000000000200
R13: 000001fb63109b96 R14: 1ffff92000000e88 R15: dffffc0000000000
ktime_get_with_offset+0x90/0x320 kernel/time/timekeeping.c:872
ktime_get_real include/linux/timekeeping.h:79 [inline]
__net_timestamp include/linux/skbuff.h:3970 [inline]
netif_rx_internal+0x37a/0x540 net/core/dev.c:4966
netif_rx+0x94/0x380 net/core/dev.c:5018
veth_forward_skb drivers/net/veth.c:297 [inline]
veth_xmit+0x62f/0xa90 drivers/net/veth.c:350
__netdev_start_xmit include/linux/netdevice.h:5036 [inline]
netdev_start_xmit include/linux/netdevice.h:5050 [inline]
xmit_one net/core/dev.c:3649 [inline]
dev_hard_start_xmit+0x2a5/0x7e0 net/core/dev.c:3665
__dev_queue_xmit+0x19df/0x2ed0 net/core/dev.c:4288
hsr_xmit net/hsr/hsr_forward.c:338 [inline]
hsr_forward_do net/hsr/hsr_forward.c:429 [inline]
hsr_forward_skb+0xfb4/0x16e0 net/hsr/hsr_forward.c:582
send_hsr_supervision_frame+0x5f7/0xb80 net/hsr/hsr_device.c:349
hsr_announce+0x162/0x300 net/hsr/hsr_device.c:405
call_timer_fn+0x16c/0x530 kernel/time/timer.c:1451
expire_timers kernel/time/timer.c:1496 [inline]
__run_timers+0x525/0x7c0 kernel/time/timer.c:1767
run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1780
handle_softirqs+0x328/0x820 kernel/softirq.c:576
__do_softirq kernel/softirq.c:610 [inline]
invoke_softirq kernel/softirq.c:450 [inline]
__irq_exit_rcu+0x12f/0x220 kernel/softirq.c:659
irq_exit_rcu+0x5/0x20 kernel/softirq.c:671
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:finish_lock_switch+0x134/0x280 kernel/sched/core.c:4804
Code: be ff ff ff ff e8 ec 75 4e 08 85 c0 74 4a 4d 85 ff 75 66 0f 1f 44 00 00 48 89 df e8 96 da 57 08 e8 11 76 2a 00 fb 48 83 c4 08 <5b> 41 5c 41 5d 41 5e 41 5f 5d c3 48 89 df e8 d9 0f fe ff 43 80 3c
RSP: 0018:ffffc90002fff6c8 EFLAGS: 00000282
RAX: d7181873f5231c00 RBX: ffff8880b903a340 RCX: d7181873f5231c00
RDX: dffffc0000000000 RSI: ffffffff8a0b1be0 RDI: ffffffff8a59e800
RBP: 1ffff11017207613 R08: dffffc0000000000 R09: ffffed1017207662
R10: ffffed1017207662 R11: 1ffff11017207661 R12: 1ffff110172075c1
R13: dffffc0000000000 R14: ffff8880b903ae08 R15: 0000000000000000
finish_task_switch+0x12f/0x640 kernel/sched/core.c:4921
context_switch kernel/sched/core.c:5052 [inline]
__schedule+0x11c3/0x4390 kernel/sched/core.c:6395
preempt_schedule_common+0x82/0xd0 kernel/sched/core.c:6571
preempt_schedule+0xa7/0xb0 kernel/sched/core.c:6596
preempt_schedule_thunk+0x16/0x18 arch/x86/entry/thunk_64.S:34
try_to_wake_up+0x701/0x1050 kernel/sched/core.c:4171
wake_up_process kernel/sched/core.c:4234 [inline]
wake_up_q+0x78/0xc0 kernel/sched/core.c:953
__mutex_unlock_slowpath+0x406/0x6a0 kernel/locking/mutex.c:895
perf_trace_init+0x20a/0x2d0 kernel/trace/trace_event_perf.c:232
perf_tp_event_init+0x89/0x110 kernel/events/core.c:10102
perf_try_init_event+0x12b/0x3d0 kernel/events/core.c:11601
perf_init_event kernel/events/core.c:11665 [inline]
perf_event_alloc+0xfcf/0x2240 kernel/events/core.c:11957
__do_sys_perf_event_open kernel/events/core.c:12495 [inline]
__se_sys_perf_event_open+0x5ae/0x1b80 kernel/events/core.c:12387
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7ff195a28749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff193c8f038 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 00007ff195c7efa0 RCX: 00007ff195a28749
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 00002000000003c0
RBP: 00007ff195aacf91 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff195c7f038 R14: 00007ff195c7efa0 R15: 00007fffccdf2e68
</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.

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