created | 2024-02-04T23:11:43Z |
---|---|
begin | 2024-01-28T00:00:00Z |
end | 2024-01-29T00:00:00Z |
path | src/sys |
commits | 7 |
date | 2024-01-28T00:40:22Z | |||
---|---|---|---|---|
author | deraadt | |||
files | src/sys/arch/alpha/conf/Makefile.alpha | log | diff | annotate |
src/sys/arch/armv7/conf/Makefile.armv7 | log | diff | annotate | |
src/sys/arch/i386/conf/Makefile.i386 | log | diff | annotate | |
src/sys/arch/landisk/conf/Makefile.landisk | log | diff | annotate | |
src/sys/arch/luna88k/conf/Makefile.luna88k | log | diff | annotate | |
src/sys/arch/macppc/conf/Makefile.macppc | log | diff | annotate | |
src/sys/arch/sparc64/conf/Makefile.sparc64 | log | diff | annotate | |
message |
set -fno-stack-protector in NORMAL_C_NOP, which is used to compile mcount.c, in the same way that -fno-ret-protector is set (because the default ret-protector is an "always" generator). This change ensures there is never a stack protector prologue/epilogue in the functions in that file, no matter what stack protector selection algorithm is in play. ok kettenis guenther |
date | 2024-01-28T01:07:26Z | |||
---|---|---|---|---|
author | deraadt | |||
files | src/sys/arch/alpha/stand/Makefile.inc | log | diff | annotate |
src/sys/arch/alpha/stand/boot/Makefile | log | diff | annotate | |
src/sys/arch/alpha/stand/nboot/Makefile | log | diff | annotate | |
src/sys/arch/alpha/stand/netboot/Makefile | log | diff | annotate | |
src/sys/arch/sparc64/stand/libsa/Makefile | log | diff | annotate | |
src/sys/arch/sparc64/stand/libz/Makefile | log | diff | annotate | |
src/sys/arch/sparc64/stand/ofwboot/Makefile | log | diff | annotate | |
message |
Force -fno-stack-protector on "boot block" that absolutely can't have a stack protector (probably not even a -fstack-protector-strong) because the bloat would render them unuseable. This also means the system compiler can now take on any more it wants, and all the pieces which can't use the stack protector are properly marked. ok kettenis |
date | 2024-01-28T03:01:39Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/pci/pucdata.c | log | diff | annotate |
message |
match on Intel C3000 tested by Stephane Tranchemer |
date | 2024-01-28T16:11:31Z | |||
---|---|---|---|---|
author | tb | |||
files | src/sys/lib/libz/deflate.c | log | diff | annotate |
src/sys/lib/libz/trees.c | log | diff | annotate | |
src/sys/lib/libz/zutil.h | log | diff | annotate | |
message | sync with userland |
date | 2024-01-28T18:42:58Z | |||
---|---|---|---|---|
author | mglocker | |||
files | src/sys/dev/pci/if_em.c | log | diff | annotate |
src/sys/dev/pci/if_em.h | log | diff | annotate | |
src/sys/dev/pci/if_em_hw.h | log | diff | annotate | |
message |
Back out the TSO support diff, since we got issues reported for which no solution could be found. Known issues at this point: 1. sparc64 panics, probably because of an alignment issue in struct tcphdr { th_off }. A diff for potentially fixing the alignment issue exists, but testing is pending. 2. Watchdogs reported on the I350 chip, which can't be reproduced on own hardware. |
date | 2024-01-28T20:34:25Z | |||
---|---|---|---|---|
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_subr.c | log | diff | annotate | |
src/sys/netinet/tcp_timer.c | log | diff | annotate | |
src/sys/netinet/udp_usrreq.c | log | diff | annotate | |
src/sys/netinet6/in6_pcb.c | log | diff | annotate | |
message |
Use more specific sockaddr type for inpcb notify. in_pcbnotifyall() is an IPv4 only function. All callers check that sockaddr dst is in fact a sockaddr_in. Pass the more spcific type and remove the runtime check at beginning of in_pcbnotifyall(). Use const sockaddr_in in in_pcbnotifyall() and const sockaddr_in6 in6_pcbnotify() as dst parameter. OK millert@ |
date | 2024-01-28T22:30:39Z | |||
---|---|---|---|---|
author | stsp | |||
files | src/sys/dev/ic/qwx.c | log | diff | annotate |
src/sys/dev/ic/qwxreg.h | log | diff | annotate | |
src/sys/dev/ic/qwxvar.h | log | diff | annotate | |
message |
add support for sending management frames to qwx(4) The initial AUTH frame is now sent when an AP is found during scans. We then receive an AUTH response from the AP. Handling this response in the driver will be our next step. |