created | 2021-10-20T09:24:00Z |
---|---|
begin | 2021-05-26T00:00:00Z |
end | 2021-05-27T00:00:00Z |
path | src/sys |
commits | 5 |
date | 2021-05-26T02:38:01Z | |||
---|---|---|---|---|
author | dlg | |||
files | src/sys/net/if_veb.c | log | diff | annotate |
message |
support divert-to when pf applies it to a packet. when a divert-to rule applies to a packet, pf doesnt take the packet away and shove it in the socket directly. pf marks the packet, and then ip (or ipv6) input processing looks at the mark and picks the local socket to queue it on. because veb operates at layer 2, ip input processing only occurred if the packet was destined to go into a vport interface. bridge(4) handles this by checking if the packet has the pf divert to mark set on it and calls ip input if it's set. this copies the semantic to veb. this allows divert-to to steal (take?) packets going over a veb and process them on a local socket. reported by ajacatot@ |
date | 2021-05-26T06:44:28Z | |||
---|---|---|---|---|
author | dlg | |||
files | src/sys/net/if_tpmr.c | log | diff | annotate |
message |
add support for pf divert-to on tpmr, like what was done for veb(4). when a divert-to rule applies to a packet, pf doesnt take the packet away and shove it in the socket directly. pf marks the packet, and then ip (or ipv6) input processing looks at the mark and picks the local socket to queue it on. because tpmr operates at layer 2, ip input has no chance to look at the packet and let the divert socket steal it. bridge(4) and now veb(4) handle this by checking if the packet has the pf divert to mark set on it and calls ip input if it's set. this copies the semantic to tpmr. |
date | 2021-05-26T08:28:34Z | |||
---|---|---|---|---|
author | mvs | |||
files | src/sys/kern/uipc_socket2.c | log | diff | annotate |
src/sys/net/pfkeyv2.c | log | diff | annotate | |
message |
Use `so_lock' to protect key management (PF_KEY) sockets. This can be done because we have no cases where one thread should lock two sockets simultaneously. tested by yasuoka@ ok bluhm@ markus@ |
date | 2021-05-26T18:11:59Z | |||
---|---|---|---|---|
author | kettenis | |||
files | src/sys/kern/sys_futex.c | log | diff | annotate |
message |
Fix the return value for the FUTEX_WAIT/FUTEX_WAIT_PRIVATE futex(2) operation. System calls should return -1 and set errno when they fail. They should not return an errno value directly. This matches how the Linux version of futex(2) behaves and what Mesa expects. This fixes a bug in Mesa where a timeout wouldn't be reported properly. Technically this is an ABI break. But libc and libpthread were changed to be compatible with both the old and new ABI, and code outside of base almost certainly expects Linux compatible behaviour. If you have not rebuilt libc and the last few days, upgrade using a snap. Mesa issue discovered by jsg@ ok mpi@, deraadt@ |
date | 2021-05-26T20:52:21Z | |||
---|---|---|---|---|
author | kettenis | |||
files | src/sys/arch/arm64/conf/GENERIC | log | diff | annotate |
src/sys/arch/arm64/conf/RAMDISK | log | diff | annotate | |
src/sys/arch/arm64/conf/files.arm64 | log | diff | annotate | |
src/sys/arch/arm64/dev/aplpmu.c | log | diff | annotate | |
src/sys/arch/arm64/dev/aplspmi.c | log | diff | annotate | |
src/sys/dev/fdt/spmivar.h | log | diff | annotate | |
message |
Add aplspmi(4), a driver for the Apple SPMI controller, and aplpmu(4) a driver for the Apple "sera" SPMI power management unit that contains the RTC on Apple M1 systems. ok patrick@ |