summaryrefslogtreecommitdiffstats
path: root/lib/libpthread/thread/thr_write.c
diff options
context:
space:
mode:
authorbrian <brian@FreeBSD.org>1998-06-14 00:56:13 +0000
committerbrian <brian@FreeBSD.org>1998-06-14 00:56:13 +0000
commit0e5f5ba899a4b90b622d4db2235bb06e2d592f50 (patch)
tree2eaeda49f72ff7ed7decb33c137a7f8ef7ab69eb /lib/libpthread/thread/thr_write.c
parent84ee66217aaf229f2db221388ca5b4bb44a24eb2 (diff)
downloadFreeBSD-src-0e5f5ba899a4b90b622d4db2235bb06e2d592f50.zip
FreeBSD-src-0e5f5ba899a4b90b622d4db2235bb06e2d592f50.tar.gz
o Pass our negotiated number of VJ slots into
sl_uncompress_tcp() and drop packets with slot numbers that are out of range. o Drop packets that want to use a slot that still has an IP header length of 0 (ie, the requested slot number is bogus again). Without this code, if the other side mis-behaves (and sends us garbage slot numbers), we happily ``adjust'' a memset(..., '\0', ...) TCP/IP header and promptly cr*p all over the stack before returning.... quickly followed by a SIGBUS. Dodgy ISP used by, and help locating the problem from: jmz Problem also seen by: Mourad de Riche <omnibus@image.dk> There's still a link lockup after this happens, but my bets are on the other side (who has already started sending rubbish) being to blame.
Diffstat (limited to 'lib/libpthread/thread/thr_write.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud