OpenBSD cvs log

created 2024-01-15T12:26:44Z
begin 2023-12-03T00:00:00Z
end 2023-12-04T00:00:00Z
path src/sys
commits 7

date 2023-12-03T00:14:53Z
author jsg
files src/sys/dev/pci/pcidevs log diff annotate
message add Intel Ethernet ids: Lunar Lake, Raptor Lake and Arrow Lake

date 2023-12-03T00:15:35Z
author jsg
files src/sys/dev/pci/pcidevs.h log diff annotate
src/sys/dev/pci/pcidevs_data.h log diff annotate
message regen

date 2023-12-03T00:19:25Z
author jsg
files src/sys/dev/pci/if_em.c log diff annotate
src/sys/dev/pci/if_em_hw.c log diff annotate
src/sys/dev/pci/if_em_hw.h log diff annotate
message match Lunar Lake, Raptor Lake and Arrow Lake

date 2023-12-03T10:50:25Z
author mvs
files src/sys/netinet/ip_ipsp.c log diff annotate
message Make ipsp_ids_gc() timeout(9) handler mpsafe. `ipsec_flows_mtx' mutex(9)
protects related data.

ok bluhm

date 2023-12-03T10:51:17Z
author mvs
files src/sys/net/rtsock.c log diff annotate
message Make rtm_senddesync_timer() timeout(9) handler mpsafe. solock() protects
the socket and the socket's PCB data.

ok bluhm

date 2023-12-03T20:24:17Z
author bluhm
files src/sys/netinet/in_pcb.c log diff annotate
src/sys/netinet/in_pcb.h log diff annotate
src/sys/netinet/tcp_usrreq.c log diff annotate
src/sys/netinet6/in6_pcb.c log diff annotate
message Use INP_IPV6 flag instead of sotopf().

During initialization in_pcballoc() sets INP_IPV6 once to avoid
reaching through inp_socket->so_proto->pr_domain->dom_family. Use
this flag consistently.

OK sashan@ mvs@

date 2023-12-03T20:36:24Z
author bluhm
files src/sys/netinet6/icmp6.c log diff annotate
src/sys/netinet6/in6_pcb.c log diff annotate
src/sys/netinet6/in6_src.c log diff annotate
src/sys/netinet6/ip6_input.c log diff annotate
src/sys/netinet6/ip6_var.h log diff annotate
src/sys/netinet6/raw_ip6.c log diff annotate
src/sys/netinet6/udp6_output.c log diff annotate
message Rename all in6p local variables to inp.

There exists no struct in6pcb in OpenBSD, this was an old kame idea.
Calling the local variable in6p does not make sense, it is actually
a struct inpcb. Also in6p is not used consistently in inet6 code.
Having the same convention for IPv4 and IPv6 is less confusing.

OK sashan@ mvs@