panic: tcpp_nucp t

0 views
Skip to first unread message

syzbot

unread,
Aug 29, 2022, 3:43:31 PM8/29/22
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ab19a69ebe1d update libfido2 to 1.11.0, taking in just ove..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=171ea583080000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=995c67b91a45861d6bf1

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

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

panic: tcpp_nucp t
kSrnrlidgagtast trasser.t
on "!_kernel_lock_held()" faiped:c(fff f"f/fsfzk5ll1r/)aaagers/multicore/kernel/sypsa/niv+/x1m_
p.c", line 2486
Parallel tracebtacpk,utput(rfffed0..0
d4e6e0) at tcp_output+0x2cd2 sys/netinet/tcp_output.c:727
tcp_send(fffffd80730869c0,fffffd805e843e00,fffffd806930cc00,fffffd8073843000) at tcp_send+0xc4 sys/netinet/tcp_usrreq.c:944
s
demp (to fefd8,7308t co,fibfed806930cc00,ffff80002baaaebpanic: knrnel diagnostic aSeaBIOS (version 1.8.2-google)
Total RAM Size = 0x0000000080000000 = 2048 MiB
CPUs found: 2 Max CPUs supported: 2
SeaBIOS (version 1.8.2-google)
Machine UUID 003a59b7-54eb-38ca-1cfb-72bc238e03e5
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=4194304 = 2048 MiB
drive 0x000f24c0: PCHS=0/0/0 translation=lba LCHS=520/128/63 s=4194304
Sending Seabios boot VM event.
Booting from Hard Disk 0...
>> OpenBSD/amd64 BOOT 3.54
boot> set $lines = 0
set: syntax error
boot> set $maxwidth = 0
set: syntax error
boot> show panic
boot: illegal argument panic
boot> trace
boot> show registers
boot> show proc
boot> ps
boot> show all locks
boot> show malloc
boot> show all pools
boot> machine ddbcpu 0
machine: syntax error
boot> trace
boot> machine ddbcpu 1
machine: syntax error
boot> trace


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

unread,
Aug 29, 2022, 4:05:14 PM8/29/22
to Greg Steuck, gr...@nest.cx, syzkaller-o...@googlegroups.com
> #syz invalid

Your 'invalid' command is accepted, but please keep syzkaller-o...@googlegroups.com mailing list in CC next time. It serves as a history of what happened with each bug report. Thank you.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "syzkaller-openbsd-bugs" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to syzkaller-openbsd...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/syzkaller-openbsd-bugs/0000000000006ba20905e7667ab2%40google.com
>> .
>>
>
>
> --
> nest.cx is Gmail hosted, use PGP:
> https://pgp.key-server.io/0x0B1542BD8DF5A1B0
> Fingerprint: 5E2B 2D0E 1E03 2046 BEC3 4D50 0B15 42BD 8DF5 A1B0
Reply all
Reply to author
Forward
0 new messages