[v5.15] BUG: soft lockup in batadv_iv_send_outstanding_bat_ogm_packet

4 views
Skip to first unread message

syzbot

unread,
Mar 9, 2023, 5:19:46 PM3/9/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d9b4a0c83a2d Linux 5.15.98
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13142dd4c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b57cfa804330c3b7
dashboard link: https://syzkaller.appspot.com/bug?extid=83373a7d8fa8f064f743
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12604584c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d6602ac80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8088989394e3/disk-d9b4a0c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2651d6753959/vmlinux-d9b4a0c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f3fa3f994f9a/Image-d9b4a0c8.gz.xz

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

watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [kworker/u4:3:278]
Modules linked in:
irq event stamp: 157055
hardirqs last enabled at (157054): [<ffff800011979450>] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:81 [inline]
hardirqs last enabled at (157054): [<ffff800011979450>] exit_to_kernel_mode+0x100/0x178 arch/arm64/kernel/entry-common.c:91
hardirqs last disabled at (157055): [<ffff800011979698>] enter_el1_irq_or_nmi+0x10/0x1c arch/arm64/kernel/entry-common.c:227
softirqs last enabled at (152046): [<ffff8000117b6734>] batadv_forw_packet_steal+0x11c/0x13c
softirqs last disabled at (152068): [<ffff8000117cbe50>] spin_lock_bh include/linux/spinlock.h:368 [inline]
softirqs last disabled at (152068): [<ffff8000117cbe50>] batadv_tt_local_commit_changes+0x24/0x44 net/batman-adv/translation-table.c:3718
CPU: 0 PID: 278 Comm: kworker/u4:3 Not tainted 5.15.98-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: bat_events batadv_iv_send_outstanding_bat_ogm_packet
pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : queued_spin_lock_slowpath+0x160/0x938 kernel/locking/qspinlock.c:382
lr : queued_spin_lock_slowpath+0x16c/0x938 kernel/locking/qspinlock.c:382
sp : ffff80001c817700
x29: ffff80001c8177a0 x28: 1ffff00003902eec x27: 1fffe0001a88ea66
x26: dfff800000000000 x25: ffff700003902ee4 x24: ffff80001c817720
x23: 1fffe0001a88ea65 x22: ffff80001c817760 x21: 0000000000000001
x20: 0000000000000001 x19: ffff0000d4475328 x18: ffff80001c817600
x17: ffff800011757834 x16: ffff80000830625c x15: 000000000000db71
x14: 000000008c8664f2 x13: ffffffffffffffff x12: 0000000000000001
x11: 1fffe0001a88ea65 x10: 0000000000000000 x9 : 0000000000000000
x8 : 0000000000000101 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff8000175c7708 x4 : 0000000000000008 x3 : ffff800008305568
x2 : 0000000000000000 x1 : 0000000000000004 x0 : 0000000000000001
Call trace:
__cmpwait_case_32 arch/arm64/include/asm/cmpxchg.h:252 [inline]
__cmpwait arch/arm64/include/asm/cmpxchg.h:278 [inline]
queued_spin_lock_slowpath+0x160/0x938 kernel/locking/qspinlock.c:382
queued_spin_lock include/asm-generic/qspinlock.h:85 [inline]
do_raw_spin_lock+0x334/0x35c kernel/locking/spinlock_debug.c:115
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:136 [inline]
_raw_spin_lock_bh+0x12c/0x1c4 kernel/locking/spinlock.c:178
spin_lock_bh include/linux/spinlock.h:368 [inline]
batadv_tt_local_commit_changes+0x24/0x44 net/batman-adv/translation-table.c:3718
batadv_iv_ogm_schedule_buff net/batman-adv/bat_iv_ogm.c:812 [inline]
batadv_iv_ogm_schedule+0x1ec/0xe10 net/batman-adv/bat_iv_ogm.c:869
batadv_iv_send_outstanding_bat_ogm_packet+0x740/0x900 net/batman-adv/bat_iv_ogm.c:1713
process_one_work+0x82c/0x1478 kernel/workqueue.c:2306
worker_thread+0x910/0x1034 kernel/workqueue.c:2453
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 <unknown>: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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages