[v6.1] BUG: soft lockup in tx

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f17b0ab65d17 Linux 6.1.25
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12652b9fc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=73f7ee8e484b74b7
dashboard link: https://syzkaller.appspot.com/bug?extid=e66a5599d722c108a809
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/553994c02131/disk-f17b0ab6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c88e4d2795a5/vmlinux-f17b0ab6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d788d429a3a9/Image-f17b0ab6.gz.xz

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

watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [aoe_tx0:2048]
Modules linked in:
irq event stamp: 30698457
hardirqs last enabled at (30698456): [<ffff8000121ba814>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (30698456): [<ffff8000121ba814>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (30698457): [<ffff8000120d83a4>] __el1_irq arch/arm64/kernel/entry-common.c:468 [inline]
hardirqs last disabled at (30698457): [<ffff8000120d83a4>] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:486
softirqs last enabled at (7396): [<ffff8000103d9af4>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (7400): [<ffff8000103d9ac0>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
CPU: 1 PID: 2048 Comm: aoe_tx0 Not tainted 6.1.25-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152 [inline]
pc : _raw_spin_unlock_irqrestore+0x58/0xac kernel/locking/spinlock.c:194
lr : __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
lr : _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
sp : ffff8000236477d0
x29: ffff8000236477d0 x28: 1fffe000183ab8c0 x27: ffff0000cb2c0c30
x26: ffff0000c1d5c600 x25: ffff0000cb2c0fd0 x24: ffff00014d2f98b0
x23: 0000000000000020 x22: 0000000000000002 x21: 0000000000000000
x20: ffff800019942e30 x19: 0000000000000000 x18: ffff800023647500
x17: 0000000000b000b0 x16: ffff800008303464 x15: 00000000000456b2
x14: 1ffff00002ab00b0 x13: dfff800000000000 x12: 0000000000000003
x11: ff8080000aabbe48 x10: 0000000000000003 x9 : 0000000000000080
x8 : 00000000000000c0 x7 : ffff80000b62ab34 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000002 x1 : ffff80001222c040 x0 : ffff80019f104000
Call trace:
arch_local_irq_restore arch/arm64/include/asm/irqflags.h:122 [inline]
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
_raw_spin_unlock_irqrestore+0x58/0xac kernel/locking/spinlock.c:194
spin_unlock_irqrestore include/linux/spinlock.h:405 [inline]
uart_write+0x358/0x878 drivers/tty/serial/serial_core.c:584
handle_tx+0x1f4/0x5f8 drivers/net/caif/caif_serial.c:236
caif_xmit+0x108/0x150 drivers/net/caif/caif_serial.c:282
__netdev_start_xmit include/linux/netdevice.h:4849 [inline]
netdev_start_xmit include/linux/netdevice.h:4863 [inline]
xmit_one net/core/dev.c:3593 [inline]
dev_hard_start_xmit+0x25c/0x9a4 net/core/dev.c:3609
__dev_queue_xmit+0x186c/0x3878 net/core/dev.c:4259
dev_queue_xmit include/linux/netdevice.h:3017 [inline]
tx+0x90/0x134 drivers/block/aoe/aoenet.c:63
kthread+0x1ac/0x374 drivers/block/aoe/aoecmd.c:1229
kthread+0x24c/0x2d4 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860


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