[v6.1] INFO: rcu detected stall in hsr_announce (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1466bf34580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=f23711a3e0b0cf750d6e
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/0d8305ca1c94/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8bc85383c07b/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d337081bce56/bzImage-f6e38ae6.xz

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

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-.... } 3726 jiffies s: 5057 root: 0x1/.
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4761 Comm: syz.7.36 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:rcu_dynticks_curr_cpu_in_eqs include/linux/context_tracking.h:-1 [inline]
RIP: 0010:rcu_is_watching+0x18/0xa0 kernel/rcu/tree.c:721
Code: e9 53 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 41 57 41 56 53 65 ff 05 bc 5a 97 7e e8 0f d2 ac 08 89 c3 83 f8 08 73 60 <49> bf 00 00 00 00 00 fc ff df 4c 8d 34 dd 80 49 5e 8c 4c 89 f0 48
RSP: 0018:ffffc900000073a0 EFLAGS: 00000093
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 95ecff323b357400
RDX: 0000000000000000 RSI: ffffffff8adef740 RDI: ffffffff8adef700
RBP: ffffc900000074c8 R08: dffffc0000000000 R09: fffffbfff1c3ed56
R10: fffffbfff1c3ed56 R11: 1ffffffff1c3ed55 R12: 0000000000000000
R13: 1ffff92000000e84 R14: 0000000000000000 R15: dffffc0000000000
FS: 00007ff3ecbfb6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b34620ff8 CR3: 0000000055c12000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
trace_lock_acquire include/trace/events/lock.h:24 [inline]
lock_acquire+0xe8/0x490 kernel/locking/lockdep.c:5633
__raw_spin_lock_irq include/linux/spinlock_api_smp.h:119 [inline]
_raw_spin_lock_irq+0x9f/0xe0 kernel/locking/spinlock.c:170
__run_hrtimer kernel/time/hrtimer.c:1751 [inline]
__hrtimer_run_queues+0x63a/0xd60 kernel/time/hrtimer.c:1811
hrtimer_interrupt+0x3c5/0x9c0 kernel/time/hrtimer.c:1873
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1107 [inline]
__sysvec_apic_timer_interrupt+0x153/0x5a0 arch/x86/kernel/apic/apic.c:1124
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
sysvec_apic_timer_interrupt+0x4d/0xc0 arch/x86/kernel/apic/apic.c:1118
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:lock_acquire+0x20f/0x490 kernel/locking/lockdep.c:5666
Code: 00 9c 8f 84 24 80 00 00 00 f6 84 24 81 00 00 00 02 0f 85 f5 00 00 00 41 f7 c6 00 02 00 00 74 01 fb 48 c7 44 24 60 0e 36 e0 45 <4b> c7 44 3d 00 00 00 00 00 66 43 c7 44 3d 09 00 00 43 c6 44 3d 0b
RSP: 0018:ffffc90000007920 EFLAGS: 00000206
RAX: 0000000000000001 RBX: 0000000000000000 RCX: 95ecff323b357400
RDX: 0000000000000000 RSI: ffffffff8a8c1700 RDI: ffffffff8adef760
RBP: ffffc90000007a28 R08: dffffc0000000000 R09: fffffbfff215c466
R10: fffffbfff215c466 R11: 1ffffffff215c465 R12: 0000000000000000
R13: 1ffff92000000f30 R14: 0000000000000246 R15: dffffc0000000000
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
_raw_spin_lock_bh+0x32/0x50 kernel/locking/spinlock.c:178
spin_lock_bh include/linux/spinlock.h:356 [inline]
send_hsr_supervision_frame+0x20c/0xa60 net/hsr/hsr_device.c:320
hsr_announce+0x18e/0x340 net/hsr/hsr_device.c:399
call_timer_fn+0x1a0/0x670 kernel/time/timer.c:1700
expire_timers kernel/time/timer.c:1751 [inline]
__run_timers+0x529/0x7d0 kernel/time/timer.c:2022
run_timer_softirq+0x63/0xf0 kernel/time/timer.c:2035
handle_softirqs+0x2a1/0x920 kernel/softirq.c:596
__do_softirq kernel/softirq.c:630 [inline]
invoke_softirq kernel/softirq.c:470 [inline]
__irq_exit_rcu+0x12f/0x220 kernel/softirq.c:679
irq_exit_rcu+0x5/0x20 kernel/softirq.c:691
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1118
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:instrument_atomic_read include/linux/instrumented.h:72 [inline]
RIP: 0010:atomic_long_read include/linux/atomic/atomic-instrumented.h:1265 [inline]
RIP: 0010:__mutex_owner kernel/locking/mutex.c:81 [inline]
RIP: 0010:mutex_spin_on_owner+0x27e/0x350 kernel/locking/mutex.c:359
Code: be 08 00 00 00 e8 d2 aa 6e 00 42 80 7c 35 00 00 74 08 4c 89 e7 e8 32 a9 6e 00 49 f7 04 24 01 00 00 00 0f 85 8c 00 00 00 f3 90 <4c> 89 e7 be 08 00 00 00 e8 a5 aa 6e 00 42 80 7c 35 00 00 0f 84 84
RSP: 0018:ffffc90003cb76a8 EFLAGS: 00000246
RAX: 1ffff1100f413b28 RBX: ffffffff8dd416d0 RCX: ffffffff81625b74
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffff88807a09d940
RBP: 1ffffffff1ba82d0 R08: dffffc0000000000 R09: ffffed100f413b29
R10: ffffed100f413b29 R11: 1ffff1100f413b28 R12: ffffffff8dd41680
R13: ffffffff8dd416d0 R14: dffffc0000000000 R15: ffff888018b40000
mutex_optimistic_spin kernel/locking/mutex.c:476 [inline]
__mutex_lock_common kernel/locking/mutex.c:607 [inline]
__mutex_lock+0x17a/0xaf0 kernel/locking/mutex.c:747
do_ipv6_setsockopt+0x336/0x3b20 net/ipv6/ipv6_sockglue.c:418
ipv6_setsockopt+0x55/0x190 net/ipv6/ipv6_sockglue.c:1024
__sys_setsockopt+0x2bf/0x3d0 net/socket.c:2288
__do_sys_setsockopt net/socket.c:2299 [inline]
__se_sys_setsockopt net/socket.c:2296 [inline]
__x64_sys_setsockopt+0xb1/0xc0 net/socket.c:2296
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff3ebd8efc9
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:00007ff3ecbfb038 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007ff3ebfe5fa0 RCX: 00007ff3ebd8efc9
RDX: 0000000000000014 RSI: 0000000000000029 RDI: 0000000000000005
RBP: 00007ff3ebe11f91 R08: 000000000000003d R09: 0000000000000000
R10: 0000200000000440 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff3ebfe6038 R14: 00007ff3ebfe5fa0 R15: 00007ffc3bcbd368
</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