[Android 6.1] BUG: soft lockup in sys_sendmsg

0 views
Skip to first unread message

syzbot

unread,
Apr 9, 2024, 2:46:21 AMApr 9
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 338203a81721 BACKPORT: mm: update mark_victim tracepoints ..
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=11952e75180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7bd1a415c6de5d9d
dashboard link: https://syzkaller.appspot.com/bug?extid=986cc2911178190351e9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=166181d3180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f3598d180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/15d0ff3824ae/disk-338203a8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/918f03d335d3/vmlinux-338203a8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f58fec5caae8/bzImage-338203a8.xz

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

watchdog: BUG: soft lockup - CPU#0 stuck for 144s! [syz-executor247:977]
Modules linked in:
CPU: 0 PID: 977 Comm: syz-executor247 Not tainted 6.1.75-syzkaller-00007-g338203a81721 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
RIP: 0010:arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
RIP: 0010:kvm_wait+0x147/0x180 arch/x86/kernel/kvm.c:1064
Code: 4c 89 e8 48 c1 e8 03 42 0f b6 04 20 84 c0 44 8b 74 24 1c 75 34 41 0f b6 45 00 44 38 f0 75 10 66 90 0f 00 2d eb 11 11 04 fb f4 <e9> 24 ff ff ff fb e9 1e ff ff ff 44 89 e9 80 e1 07 38 c1 7c a3 4c
RSP: 0018:ffffc900018a7780 EFLAGS: 00000246
RAX: 0000000000000003 RBX: 1ffff92000314ef4 RCX: ffffffff84ff6d9c
RDX: dffffc0000000000 RSI: 0000000000000003 RDI: ffff888121e7b798
RBP: ffffc900018a7830 R08: dffffc0000000000 R09: ffffed10243cf6f4
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888121e7b798 R14: 0000000000000003 R15: 1ffff92000314ef8
FS: 00007ff57f1e66c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000000 CR3: 00000001221bd000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
<TASK>
pv_wait arch/x86/include/asm/paravirt.h:603 [inline]
pv_wait_head_or_lock kernel/locking/qspinlock_paravirt.h:470 [inline]
__pv_queued_spin_lock_slowpath+0x6de/0xda0 kernel/locking/qspinlock.c:511
pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:591 [inline]
queued_spin_lock_slowpath arch/x86/include/asm/qspinlock.h:51 [inline]
queued_spin_lock include/asm-generic/qspinlock.h:114 [inline]
do_raw_spin_lock include/linux/spinlock.h:186 [inline]
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:127 [inline]
_raw_spin_lock_bh+0x139/0x1b0 kernel/locking/spinlock.c:178
spin_lock_bh include/linux/spinlock.h:355 [inline]
lock_sock_nested+0x92/0x300 net/core/sock.c:3502
lock_sock include/net/sock.h:1758 [inline]
tipc_sendstream+0x47/0x70 net/tipc/socket.c:1549
sock_sendmsg_nosec net/socket.c:716 [inline]
__sock_sendmsg net/socket.c:728 [inline]
____sys_sendmsg+0x5d3/0x9a0 net/socket.c:2504
___sys_sendmsg net/socket.c:2558 [inline]
__sys_sendmsg+0x2a9/0x390 net/socket.c:2587
__do_sys_sendmsg net/socket.c:2596 [inline]
__se_sys_sendmsg net/socket.c:2594 [inline]
__x64_sys_sendmsg+0x7f/0x90 net/socket.c:2594
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7ff57f2253e9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 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:00007ff57f1e6228 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000000000d RCX: 00007ff57f2253e9
RDX: 0000000000000000 RSI: 0000000020000780 RDI: 0000000000000004
RBP: 00007ff57f2af328 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ff57f2af320
R13: 00007ff57f2af32c R14: 00007ffd0ac32db0 R15: 00007ffd0ac32e98
</TASK>


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