panic: receive 1: so ADDR, so_type 3, sb_cc 176

1 view
Skip to first unread message

syzbot

unread,
Oct 28, 2019, 5:06:09 AM10/28/19
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: c2f6c1bf Mark the _Qp_{mul,div,add,sub} functions as 'prot..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=128bf674e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d0fe83f82fe104d4
dashboard link: https://syzkaller.appspot.com/bug?extid=670e63f331abb6de7180

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

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

panic: receive 1: so 0xfffffd803700f480, so_type 3, sb_cc 176
Stopped at db_enter+0x18: addq $0x8,%rsp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*290938 81883 0 0 0 0 dhclient
db_enter() at db_enter+0x18 sys/arch/amd64/amd64/db_interface.c:398
panic() at panic+0x15c sys/kern/subr_prf.c:207
soreceive(fffffd803700f480,0,ffff8000148867b8,0,0,ffff8000148866c4) at
soreceive+0x16ac sys/kern/uipc_socket.c:798
soo_read(fffffd803b47a0f0,ffff8000148867b8,0) at soo_read+0x53
sys/kern/sys_socket.c:70
dofilereadv(ffff8000ffff93c8,6,ffff8000148867b8,0,ffff8000148868a0) at
dofilereadv+0x1a2 sys/kern/sys_generic.c:236
sys_read(ffff8000ffff93c8,ffff800014886850,ffff8000148868a0) at
sys_read+0x83 sys/kern/sys_generic.c:156
syscall(ffff800014886920) at syscall+0x507 sys/arch/amd64/amd64/trap.c:555
Xsyscall(6,3,7f7ffffe57a8,3,fc8df584,1f6c51e29000) at Xsyscall+0x128
end of kernel
end trace frame: 0x7f7ffffe54e0, count: 7
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports. Insufficient info makes it difficult to find and fix bugs.


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Jan 26, 2020, 4:06:06 AM1/26/20
to syzkaller-o...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages