[v6.1] BUG: soft lockup in tx (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e5c3b988b827 Linux 6.1.76
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=178c1988180000
kernel config: https://syzkaller.appspot.com/x/.config?x=907f7acef7540378
dashboard link: https://syzkaller.appspot.com/bug?extid=f22967866b403254bdaa
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fd64649e0495/disk-e5c3b988.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/257d7545589e/vmlinux-e5c3b988.xz
kernel image: https://storage.googleapis.com/syzbot-assets/25a59d22a12c/Image-e5c3b988.gz.xz

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

watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [aoe_tx0:2050]
Modules linked in:
irq event stamp: 32380253
hardirqs last enabled at (32380252): [<ffff80001222e8a4>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (32380252): [<ffff80001222e8a4>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (32380253): [<ffff80001214a7f4>] __el1_irq arch/arm64/kernel/entry-common.c:468 [inline]
hardirqs last disabled at (32380253): [<ffff80001214a7f4>] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:486
softirqs last enabled at (6242): [<ffff800010430634>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (6246): [<ffff800010430600>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
CPU: 0 PID: 2050 Comm: aoe_tx0 Not tainted 6.1.76-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/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 : ffff800023d477d0
x29: ffff800023d477d0 x28: 1fffe000231068c0 x27: ffff0000cd9b0c30
x26: ffff000118834600 x25: ffff0000cd9b0fd0 x24: ffff0000cc7a10b0
x23: 0000000000000020 x22: 0000000000000002 x21: 0000000000000000
x20: ffff800019c15ed0 x19: 0000000000000000 x18: ffff800023d47500
x17: ffff8000188c8000 x16: ffff800008304a58 x15: ffff8000183adf80
x14: 1ffff00002b080b0 x13: dfff800000000000 x12: 0000000000000003
x11: 0000000000ff0100 x10: 0000000000000003 x9 : 0000000000000080
x8 : 00000000000000c0 x7 : ffff80000b64eb3c x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000002 x1 : ffff8000122ac560 x0 : ffff80019ebcc000
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:582
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:4853 [inline]
netdev_start_xmit include/linux/netdevice.h:4867 [inline]
xmit_one net/core/dev.c:3627 [inline]
dev_hard_start_xmit+0x25c/0x9a4 net/core/dev.c:3643
__dev_queue_xmit+0x186c/0x38d8 net/core/dev.c:4293
dev_queue_xmit include/linux/netdevice.h:3021 [inline]
tx+0x90/0x134 drivers/block/aoe/aoenet.c:63
kthread+0x1ac/0x374 drivers/block/aoe/aoecmd.c:1229
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864


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