OpenBSD cvs log

created 2019-04-30T03:51:15Z
begin 2019-03-04T00:00:00Z
end 2019-03-05T00:00:00Z
path src/sys
commits 7

date 2019-03-04T01:06:48Z
author dhill
files src/sys/sys/buf.h log diff annotate
message Make sure we clear all valid bytes in clrbuf.

ok deraadt@

date 2019-03-04T07:09:54Z
author deraadt
files src/sys/kern/uipc_syscalls.c log diff annotate
message Yet another (unsigned) cast who's only purpose is to incorrectly truncate
a size_t. Multiply-overflow is checked beforehands. If this could (it can't)
validly be more than 4GB, the (unsigned) is a truncation and causes copyin of
insufficient data, without indicating error...
ok claudio

date 2019-03-04T08:42:12Z
author stsp
files src/sys/net/pfkeyv2.h log diff annotate
src/sys/net/pfkeyv2_convert.c log diff annotate
message Add padding to struct sadb_x_counter to make it comply with
alignment constraints documented in RFC 2367 section 2.2.
Fixes 'ipsecctl -ss' segfault observed on i386.
with and ok deraadt@ visa@ mikeb@

date 2019-03-04T18:41:40Z
author denis
files src/sys/net/if_pppx.c log diff annotate
message allow IPv6 to flow through pppx(4)

OK phessler@ deraadt@

date 2019-03-04T19:23:02Z
author anton
files src/sys/kern/tty_pty.c log diff annotate
message When closing the slave end of a pty, generate an EOF event to any kqueue
consumer of the master end. This behavior is equivalent to how pipes
already behave with kqueue. Also, FreeBSD and NetBSD behaves the same

ok deraadt@ millert@

date 2019-03-04T21:34:08Z
author dlg
files src/sys/net/ifq.c log diff annotate
message don't need to initialise qdrops twice when setting up ifqs and ifiqs.

date 2019-03-04T21:57:16Z
author dlg
files src/sys/net/ifq.c log diff annotate
message move back to ifiq_input counting packets instead of queue operations.

the backpressure seems to have kicked in too early, introducing a
lot of packet loss where there wasn't any before. secondly, counting
operations interacted extremely badly with pseudo-interfaces. for
example, if you have a physical interface that rxes 100 vlan
encapsulated packets, it will call ifiq_input once for all 100
packets. when the network stack is running vlan_input against thes
packets, vlan_input will take the packet and call ifiq_input against
each of them. because the stack is running packets on the parent
interface, it can't run the packets on the vlan interface, so you
end up with ifiq_input being called 100 times, and we dropped packets
after 16 calls to ifiq_input without a matching run of the stack.

chris cappuccio hit some weird stuff too.

discussed with claudio@