[v5.15] BUG: soft lockup in tx

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d86dfc4d95cd Linux 5.15.106
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15739c87c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=639d55ab480652c5
dashboard link: https://syzkaller.appspot.com/bug?extid=c42867a2a4f8909349ca
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/b2a94107dd69/disk-d86dfc4d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/398f8d288cb9/vmlinux-d86dfc4d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9b790c7e7c8c/Image-d86dfc4d.gz.xz

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

watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [aoe_tx0:2047]
Modules linked in:
irq event stamp: 19470333
hardirqs last enabled at (19470332): [<ffff800011a14320>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
hardirqs last enabled at (19470332): [<ffff800011a14320>] _raw_spin_unlock_irqrestore+0xac/0x158 kernel/locking/spinlock.c:194
hardirqs last disabled at (19470333): [<ffff80001193f010>] enter_el1_irq_or_nmi+0x10/0x1c arch/arm64/kernel/entry-common.c:227
softirqs last enabled at (4434): [<ffff80000fd80398>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (4446): [<ffff80000fd80364>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
CPU: 1 PID: 2047 Comm: aoe_tx0 Not tainted 5.15.106-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:161 [inline]
pc : _raw_spin_unlock_irqrestore+0xbc/0x158 kernel/locking/spinlock.c:194
lr : __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
lr : _raw_spin_unlock_irqrestore+0xac/0x158 kernel/locking/spinlock.c:194
sp : ffff8000225a7800
x29: ffff8000225a7810 x28: ffff0000cc0a7e30 x27: ffff0000cc0a7dc0
x26: ffff0000cf168ca8 x25: ffff0000d9286018 x24: 0000000000000000
x23: dfff800000000000 x22: ffff80000b435790 x21: ffff8000186fabc0
x20: ffff8000186faba8 x19: 0000000000000000 x18: ffff8000225a7520
x17: ff8080000fd79a9c x16: ffff8000082e9784 x15: 0000000000037e66
x14: 1ffff0000291a06a x13: ffffffffffffffff x12: 0000000000000000
x11: ff8080000a99c964 x10: 0000000000000003 x9 : 0000000000000080
x8 : 00000000000000c0 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff800008045814
x2 : 0000000000000002 x1 : ffff800011a9a980 x0 : ffff80019fffe000
Call trace:
arch_local_irq_restore arch/arm64/include/asm/irqflags.h:122 [inline]
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
_raw_spin_unlock_irqrestore+0xbc/0x158 kernel/locking/spinlock.c:194
spin_unlock_irqrestore include/linux/spinlock.h:418 [inline]
uart_write_room+0x168/0x300 drivers/tty/serial/serial_core.c:603
tty_write_room+0x6c/0x8c drivers/tty/tty_ioctl.c:79
handle_tx+0x124/0x644 drivers/net/caif/caif_serial.c:226
caif_xmit+0x10c/0x160 drivers/net/caif/caif_serial.c:282
__netdev_start_xmit include/linux/netdevice.h:5019 [inline]
netdev_start_xmit include/linux/netdevice.h:5033 [inline]
xmit_one net/core/dev.c:3592 [inline]
dev_hard_start_xmit+0x2bc/0x92c net/core/dev.c:3608
__dev_queue_xmit+0x13a8/0x2a6c net/core/dev.c:4223
dev_queue_xmit+0x24/0x34 net/core/dev.c:4256
tx+0x8c/0x130 drivers/block/aoe/aoenet.c:63
kthread+0x1ac/0x374 drivers/block/aoe/aoecmd.c:1230
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870


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