Hello,
syzbot found the following issue on:
HEAD commit: ac7079a42ea5 Linux 6.1.137
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=140998f4580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=51883bd03903e09
dashboard link:
https://syzkaller.appspot.com/bug?extid=0608299c38bdd431c9e2
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.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/309e93338812/disk-ac7079a4.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/869869c85b32/vmlinux-ac7079a4.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/d4b50ed751d5/Image-ac7079a4.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+060829...@syzkaller.appspotmail.com
watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [aoe_tx0:2062]
Modules linked in:
irq event stamp: 34113377
hardirqs last enabled at (34113376): [<ffff8000119ff30c>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (34113376): [<ffff8000119ff30c>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (34113377): [<ffff800011914108>] __el1_irq arch/arm64/kernel/entry-common.c:468 [inline]
hardirqs last disabled at (34113377): [<ffff800011914108>] el1_interrupt+0x24/0x54 arch/arm64/kernel/entry-common.c:486
softirqs last enabled at (1036): [<ffff80000fcff810>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (1040): [<ffff80000fcff7dc>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
CPU: 0 PID: 2062 Comm: aoe_tx0 Not tainted 6.1.137-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
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 : ffff8000269f7840
x29: ffff8000269f7840 x28: ffff0000f1dd01b0 x27: ffff0000c34cf000
x26: ffff0000f1dd0140 x25: 1fffe00019d17196 x24: 0000000000000000
x23: 0000000000000000 x22: dfff800000000000 x21: ffff0000cded0fd8
x20: ffff80001c609a90 x19: 0000000000000000 x18: ffff800011a7bd00
x17: ffff8000181a0000 x16: ffff8000082d1c08 x15: ffff800017c80fc0
x14: ffff0000d106a658 x13: 1ffff00002a0e0b1 x12: 0000000000ff0100
x11: ff0080000a889074 x10: 0000000000000003 x9 : 0000000000000080
x8 : 00000000000000c0 x7 : ffff80000b34d270 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000002 x1 : ffff800011a7d800 x0 : ffff80019ee50000
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:406 [inline]
uart_write_room+0x150/0x2d4 drivers/tty/serial/serial_core.c:615
tty_write_room+0x6c/0x8c drivers/tty/tty_ioctl.c:80
handle_tx+0x120/0x5f8 drivers/net/caif/caif_serial.c:226
caif_xmit+0x108/0x150 drivers/net/caif/caif_serial.c:282
__netdev_start_xmit include/linux/netdevice.h:4896 [inline]
netdev_start_xmit include/linux/netdevice.h:4910 [inline]
xmit_one net/core/dev.c:3658 [inline]
dev_hard_start_xmit+0x244/0x8e0 net/core/dev.c:3674
__dev_queue_xmit+0x155c/0x309c net/core/dev.c:4334
dev_queue_xmit include/linux/netdevice.h:3051 [inline]
tx+0x9c/0x1c8 drivers/block/aoe/aoenet.c:63
kthread+0x160/0x330 drivers/block/aoe/aoecmd.c:1237
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