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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cdfd0a7f0139 Linux 5.15.154
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=135a2add180000
kernel config: https://syzkaller.appspot.com/x/.config?x=618bf6f66d00ead6
dashboard link: https://syzkaller.appspot.com/bug?extid=f37ed25462439c904d62
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3415077c9536/disk-cdfd0a7f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/533465635bfa/vmlinux-cdfd0a7f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/96055d520f96/bzImage-cdfd0a7f.xz

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

rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 1-....: (10500 ticks this GP) idle=c71/1/0x4000000000000000 softirq=14020/14020 fqs=5243
(t=10502 jiffies g=18813 q=890)
NMI backtrace for cpu 1
CPU: 1 PID: 1381 Comm: aoe_tx0 Not tainted 5.15.154-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2d0 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:349
print_cpu_stall+0x320/0x600 kernel/rcu/tree_stall.h:633
check_cpu_stall kernel/rcu/tree_stall.h:727 [inline]
rcu_pending kernel/rcu/tree.c:3932 [inline]
rcu_sched_clock_irq+0x8d9/0x1150 kernel/rcu/tree.c:2619
update_process_times+0x196/0x200 kernel/time/timer.c:1818
tick_sched_handle kernel/time/tick-sched.c:254 [inline]
tick_sched_timer+0x386/0x550 kernel/time/tick-sched.c:1473
__run_hrtimer kernel/time/hrtimer.c:1686 [inline]
__hrtimer_run_queues+0x55b/0xcf0 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1812
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1085 [inline]
__sysvec_apic_timer_interrupt+0x139/0x470 arch/x86/kernel/apic/apic.c:1102
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1096
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:161 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0xd4/0x130 kernel/locking/spinlock.c:194
Code: 9c 8f 44 24 20 42 80 3c 23 00 74 08 4c 89 f7 e8 12 12 a3 f7 f6 44 24 21 02 75 4e 41 f7 c7 00 02 00 00 74 01 fb bf 01 00 00 00 <e8> 67 54 30 f7 65 8b 05 18 63 db 75 85 c0 74 3f 48 c7 04 24 0e 36
RSP: 0018:ffffc9000548f900 EFLAGS: 00000206
RAX: d90f01458bbeb900 RBX: 1ffff92000a91f24 RCX: ffffffff81631878
RDX: dffffc0000000000 RSI: ffffffff8a8b2a00 RDI: 0000000000000001
RBP: ffffc9000548f990 R08: dffffc0000000000 R09: fffffbfff1f7ec4b
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff92000a91f20 R14: ffffc9000548f920 R15: 0000000000000246
spin_unlock_irqrestore include/linux/spinlock.h:418 [inline]
uart_write+0x3ae/0x930 drivers/tty/serial/serial_core.c:572
handle_tx+0x249/0x620 drivers/net/caif/caif_serial.c:236
__netdev_start_xmit include/linux/netdevice.h:5019 [inline]
netdev_start_xmit include/linux/netdevice.h:5033 [inline]
xmit_one net/core/dev.c:3617 [inline]
dev_hard_start_xmit+0x298/0x7a0 net/core/dev.c:3633
__dev_queue_xmit+0x1cee/0x3230 net/core/dev.c:4248
tx+0x65/0x160 drivers/block/aoe/aoenet.c:63
kthread+0x234/0x440 drivers/block/aoe/aoecmd.c:1230
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
</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