hastd: Use fixed-length protocol names
All communication between hastd nodes and internally between hastd and
its worker children passes through the same pair of send / receive
functions. The receive function uses recv(2) with the MSG_WAITALL flag,
which in theory means we should never get a short read. However, when
handing off a socket to a worker child, we also pass a variable-length
string identifying the type of socket we're passing, and reading this
string relies on a short read. This used to work because the arrival of
the descriptor would interrupt the recv(2) call, but this bug was fixed
when the AF_UNIX code was rewritten a while ago and hastd has been
broken ever since.
Fixing the length of the protocol name to four characters including the
terminating null solves the short-read bug by never requiring a short
read (nothing else in hastd requires one).
Note that this issue appears to have been reported independently first
by Alessandro Sagratini in PR 234576 and then by Martin Vidovic in
[9 lines not shown]
acpi: Increase length of time (1s -> 5s) for quirk
The ACPI quirk on Framework Laptop 12 firmware was previously clocked
at ~620 ms for a Notify 0x80 replayed on power-button press to wake.
However, when KMS is not loaded, that very same notification comes in
past the 1s we previously allowed.
Use the already-defined ACPI_MINIMUM_AWAKETIME (5) seconds as our new
boundary so that we can successfully come out of S3 on this hardware.
Introduce new tunable hw.acpi.button_replay_window
Reviewed by: obiwac, olce
Differential Revision: https://reviews.freebsd.org/D59583
ppp: Fix address leaks
Avoid printing timer addresses, so as to not divulge information about
the address space layout.
In ip.c, print the actual SPI instead of a pointer to the SPI in the
header buffer.
When debug logging is enabled, don't leak pointers when logging function
arguments or return values.
Reported by: Reo Shiseki
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
tcp: Create fewer per-VNET zones
We have a problem in UMA where creating new zones requires a traversal
of all existing zones (in order to find a unique name for the vm.uma
sysctl subtree). This means that per-VNET UMA zones can be expensive to
create if one creates many VNET jails in a row. This itself is a
problem, but I don't see a quick solution.
Ideally we would avoid creating per-VNET zones in the first place
(except when the desire to impose per-VNET limits necessitates this),
and it turns out that the TCP fastopen and SACK code create several of
these for no apparent reason.
So: make fastopen and SACK zones global. Move some fastopen structure
definitions into tcp_fastopen.c, as they don't need to be public.
Reported by: bapt ("creating many VNET jails in a row is slow")
Reviewed by: tuexen, glebius
MFC after: 3 weeks
Differential Revision: https://reviews.freebsd.org/D59708
tslog.4: Canonicalize SYNOPSIS
Also, add the missing blank comment line at the top of the file.
Event: EuroBSDcon 2026
MFC after: 3 days
(cherry picked from commit dc867c353c8b423131f7f6a7f687c86713bf0666)
wpa_supplicant.8: Renew SEE ALSO + tag SPDX
- remove old wifi drivers, these are very old and we have many more
- add quick start guide to connecting to wifi
Event: EuroBSDCon 2026
MFC after: 3 days
Reviewed by: bz, emaste
Differential Revision: https://reviews.freebsd.org/D59615
(cherry picked from commit d5c09e32ce8aa625ab9429c5fe87137fb92bff53)
tun.4: Canonicalize SYNOPSIS and AUTHORS
While here, s/PR#2411/NetBSD PR#2411/ in the comments for clarity.
I had to go to netbsd sources to get this information.
MFC after: 3 days
Event: Berlin Hackathon 202609
(cherry picked from commit 555972c6c94721bffbff1ecb51d916977b5c85f7)
nvd.4: Canonicalize SYNOPSIS, TUNABLES, tag SPDX
MFC after: 3 days
Event: Berlin Hackathon 202609
(cherry picked from commit 04f53c5fa4cc8109fb263c6eed3b3c45099411f5)
ntb.4: Canonicalize SYNOPSIS and LOADER TUNABLES
Also tag SPDX, and switch X to %d for clarity and consistency.
MFC after: 3 days
(cherry picked from commit 9cdadb31f30251552e112a6fba23acfc6de5cc8b)
