[Android 5.10] BUG: soft lockup in sys_recvmsg (2)

0 views
Skip to first unread message

syzbot

unread,
Apr 22, 2025, 11:10:26 PMApr 22
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ba8b8b193394 Revert "can: statistics: use atomic access in..
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=111446cc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d0d5a25afd717f7c
dashboard link: https://syzkaller.appspot.com/bug?extid=e5414df1a654fb81ab5e
compiler: Debian clang version 15.0.6, Debian LLD 15.0.6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13149a6f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17481990580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/024c8f4768cd/disk-ba8b8b19.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b9fb5931f0e6/vmlinux-ba8b8b19.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2d8539f82fe0/bzImage-ba8b8b19.xz

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

watchdog: BUG: soft lockup - CPU#1 stuck for 123s! [syz-executor586:3369]
Modules linked in:
CPU: 1 PID: 3369 Comm: syz-executor586 Not tainted 5.10.236-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:arch_atomic_try_cmpxchg arch/x86/include/asm/atomic.h:-1 [inline]
RIP: 0010:atomic_try_cmpxchg_acquire include/asm-generic/atomic-instrumented.h:707 [inline]
RIP: 0010:queued_spin_lock include/asm-generic/qspinlock.h:82 [inline]
RIP: 0010:do_raw_spin_lock include/linux/spinlock.h:183 [inline]
RIP: 0010:__raw_spin_lock_bh include/linux/spinlock_api_smp.h:136 [inline]
RIP: 0010:_raw_spin_lock_bh+0xc0/0x1b0 kernel/locking/spinlock.c:175
Code: fc 4c 89 ff be 04 00 00 00 e8 6c 0c f5 fc 43 0f b6 04 26 84 c0 0f 85 aa 00 00 00 8b 44 24 20 b9 01 00 00 00 f0 41 0f b1 4d 00 <75> 33 48 c7 04 24 0e 36 e0 45 49 c7 04 1c 00 00 00 00 65 48 8b 04
RSP: 0018:ffffc90003e16260 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 1ffff920007c2c4c RCX: 0000000000000001
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffffc90003e16280
RBP: ffffc90003e162f0 R08: dffffc0000000000 R09: 0000000000000003
R10: fffff520007c2c50 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffffc90003e16794 R14: 1ffff920007c2c50 R15: ffffc90003e16280
FS: 00007fbc80e356c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbc80e35d58 CR3: 0000000114192000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
spin_lock_bh include/linux/spinlock.h:359 [inline]
tipc_skb_peek_port net/tipc/msg.h:1248 [inline]
tipc_sk_rcv+0x2d6/0x1e30 net/tipc/socket.c:2487
tipc_node_xmit+0x34b/0xe30 net/tipc/node.c:1674
tipc_node_xmit_skb net/tipc/node.c:1739 [inline]
tipc_node_distr_xmit+0x36a/0x4d0 net/tipc/node.c:1754
tipc_sk_rcv+0x177d/0x1e30 net/tipc/socket.c:2497
tipc_node_xmit+0x34b/0xe30 net/tipc/node.c:1674
tipc_sk_push_backlog+0x4da/0x7b0 net/tipc/socket.c:1306
tipc_sk_conn_proto_rcv net/tipc/socket.c:1358 [inline]
tipc_sk_proto_rcv+0xaa9/0x1db0 net/tipc/socket.c:2156
tipc_sk_filter_rcv+0x3603/0x3e00 net/tipc/socket.c:2350
tipc_sk_enqueue net/tipc/socket.c:2442 [inline]
tipc_sk_rcv+0x8a1/0x1e30 net/tipc/socket.c:2493
tipc_node_xmit+0x34b/0xe30 net/tipc/node.c:1674
tipc_node_xmit_skb net/tipc/node.c:1739 [inline]
tipc_node_distr_xmit+0x36a/0x4d0 net/tipc/node.c:1754
tipc_sk_backlog_rcv+0x18b/0x210 net/tipc/socket.c:2410
sk_backlog_rcv include/net/sock.h:1052 [inline]
__release_sock+0x148/0x410 net/core/sock.c:2583
release_sock+0x65/0x1b0 net/core/sock.c:3134
tipc_wait_for_rcvmsg+0x311/0x630 net/tipc/socket.c:1849
tipc_recvstream+0x292/0xf70 net/tipc/socket.c:2040
____sys_recvmsg+0x286/0x530 net/socket.c:-1
___sys_recvmsg+0x1ec/0x690 net/socket.c:2637
__sys_recvmsg net/socket.c:2667 [inline]
__do_sys_recvmsg net/socket.c:2677 [inline]
__se_sys_recvmsg net/socket.c:2674 [inline]
__x64_sys_recvmsg+0x1ee/0x2c0 net/socket.c:2674
do_syscall_64+0x31/0x40 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fbc80e95f49
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 81 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbc80e35218 EFLAGS: 00000246 ORIG_RAX: 000000000000002f
RAX: ffffffffffffffda RBX: 00007fbc80e356c0 RCX: 00007fbc80e95f49
RDX: 0000000000000000 RSI: 0000200000000080 RDI: 0000000000000003
RBP: 00007fbc80f203f8 R08: 00007ffe4d2e0d87 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000200000000240
R13: 00007fbc80f203f0 R14: 0000200000000880 R15: 0000200000000090
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 3368 Comm: syz-executor586 Not tainted 5.10.236-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:native_restore_fl arch/x86/include/asm/irqflags.h:41 [inline]
RIP: 0010:arch_local_irq_restore arch/x86/include/asm/irqflags.h:84 [inline]
RIP: 0010:kvm_wait+0xfc/0x150 arch/x86/kernel/kvm.c:926
Code: 38 f0 75 26 41 f7 c7 00 02 00 00 75 0f 0f 1f 44 00 00 0f 00 2d 65 5d d5 03 f4 eb 0e 0f 1f 44 00 00 0f 00 2d 56 5d d5 03 fb f4 <4c> 89 7c 24 18 ff 74 24 18 9d 48 c7 44 24 20 0e 36 e0 45 49 c7 04
RSP: 0018:ffffc90003dd7680 EFLAGS: 00000246
RAX: 0000000000000003 RBX: 1ffff920007baed4 RCX: ffffffff8150d8d4
RDX: 0000000000000001 RSI: 0000000000000003 RDI: ffffc90003dd76c0
RBP: ffffc90003dd7730 R08: dffffc0000000000 R09: ffffed1021929292
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88810c949488 R14: 0000000000000003 R15: 0000000000000246
FS: 00007fbc80e566c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000000 CR3: 0000000114192000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
pv_wait arch/x86/include/asm/paravirt.h:564 [inline]
pv_wait_head_or_lock kernel/locking/qspinlock_paravirt.h:470 [inline]
__pv_queued_spin_lock_slowpath+0x72f/0xc70 kernel/locking/qspinlock.c:508
pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:554 [inline]
queued_spin_lock_slowpath arch/x86/include/asm/qspinlock.h:51 [inline]
queued_spin_lock include/asm-generic/qspinlock.h:85 [inline]
do_raw_spin_lock include/linux/spinlock.h:183 [inline]
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:136 [inline]
_raw_spin_lock_bh+0x139/0x1b0 kernel/locking/spinlock.c:175
spin_lock_bh include/linux/spinlock.h:359 [inline]
lock_sock_nested+0x92/0x300 net/core/sock.c:3117
lock_sock include/net/sock.h:1648 [inline]
tipc_sendstream+0x47/0x70 net/tipc/socket.c:1540
sock_sendmsg_nosec net/socket.c:652 [inline]
__sock_sendmsg net/socket.c:664 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2376
___sys_sendmsg+0x252/0x2e0 net/socket.c:2430
__sys_sendmsg net/socket.c:2459 [inline]
__do_sys_sendmsg net/socket.c:2468 [inline]
__se_sys_sendmsg+0x1b1/0x280 net/socket.c:2466
__x64_sys_sendmsg+0x7b/0x90 net/socket.c:2466
do_syscall_64+0x31/0x40 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fbc80e95f49
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 81 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbc80e56218 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000033 RCX: 00007fbc80e95f49
RDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000004
RBP: 00007fbc80f203e8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000200000000240
R13: 00007fbc80f203e0 R14: 0000200000000880 R15: 0000200000000090


---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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
Reply all
Reply to author
Forward
0 new messages