Fix dumpfs to allow NAME=wedge-label on command line
This is a follow-on from the PR bin/59957 changes, and is being
included with that PR so it is easier to locate all the tools that
have been changed this way, so they can all be updated again once
the new code is moved to libutil where it belongs, and out of src/sbin/fsck.
When handling of NAME=whatever was added to dumpfs, it was done
in a way where it could only work when dumpfs was used as
dumpfs mount-point
and /etc/fsck contained
NAME=whatever mount-point [rest of fstab entry]
That covers the vast majority of actual uses, but a simple
dumpfs NAME=whatever
[5 lines not shown]
Pull up following revision(s) (requested by skrll in ticket #279):
common/lib/libc/atomic/atomic_cas_16_cas.c: revision 1.4
common/lib/libc/atomic/atomic_cas_16_cas.c: revision 1.5
common/lib/libc/atomic/atomic_cas_8_cas.c: revision 1.4
common/lib/libc/atomic/atomic_cas_32_cas.c: revision 1.3
common/lib/libc/atomic/atomic_cas_8_cas.c: revision 1.5
common/lib/libc/atomic/atomic_cas_8_cas.c: revision 1.6
tests/lib/libc/atomic/t___sync_compare_and_swap.c: revision 1.4
tests/lib/libc/atomic/t___sync_compare_and_swap.c: revision 1.5
common/lib/libc/atomic/atomic_init_testset.c: revision 1.22
common/lib/libc/atomic/atomic_init_testset.c: revision 1.23
common/lib/libc/atomic/atomic_cas_64_cas.c: revision 1.4
common/lib/libc/atomic/atomic_cas_by_cas32.c: revision 1.5
PR/56839 GCC emits wrong codes for compare_and_swap_1 bultins on armv5 (el & eb)
There is mismatch in signedness of the GCC builtin __sync_* function arguments
and the _atomic_* functions so we cannot directly alias them. Instead write
[13 lines not shown]
Pull up following revision(s) (requested by mrg in ticket #277):
sys/fs/cd9660/cd9660_rrip.c: revision 1.19
cd9660: make sure that NM records are at least 5 bytes long.
avoids an integer underflow when this length has 5 subtracted from it
for a later path.
Reported by Adam Crosser, Praetorian
Pull up the following, requested by christos in ticket #272:
crypto/external/apache2/openssl/lib/libcrypto/man/OPENSSL_ppccap.3 up to 1.2
crypto/external/apache2/openssl/lib/libcrypto/man/BIO_set_flags.3 up to 1.2
crypto/external/apache2/openssl/lib/libcrypto/man/CMS_EncryptedData_set1_key.3 up to 1.2
crypto/external/apache2/openssl/lib/libcrypto/man/EVP_CIPHER_CTX_get_app_data.3 up to 1.2
crypto/external/apache2/openssl/lib/libcrypto/man/openssl-DES_random_key.3 up to 1.2
crypto/external/apache2/openssl/lib/libcrypto/man/openssl-HMAC.3 up to 1.2
crypto/external/apache2/openssl/lib/libcrypto/man/openssl-MD5.3 up to 1.2
crypto/external/apache2/openssl/dist/crypto/modes/asm/aes-gcm-ppc-v1.pl up to 1.1
crypto/external/apache2/openssl/dist/doc/man3/BIO_set_flags.pod up to 1.1.1.1
crypto/external/apache2/openssl/dist/doc/man3/CMS_EncryptedData_set1_key.pod up to 1.1.1.1
crypto/external/apache2/openssl/dist/doc/man3/EVP_CIPHER_CTX_get_app_data.pod up to 1.1.1.1
crypto/external/apache2/openssl/dist/doc/man3/OPENSSL_ppccap.pod up to 1.1.1.1
crypto/external/apache2/openssl/dist/doc/man3/X509V3_EXT_print.pod up to 1.1.1.1
crypto/external/apache2/openssl/dist/test/certs/cve-2026-28388-ca.pem up to 1.1.1.1
crypto/external/apache2/openssl/dist/test/certs/cve-2026-28388-crls.pem up to 1.1.1.1
crypto/external/apache2/openssl/dist/test/certs/cve-2026-28388-leaf.pem up to 1.1.1.1
crypto/external/apache2/openssl/dist/test/certs/ext-timeSpecification-periodic-no-second.pem up to 1.1.1.1
[3249 lines not shown]
Pull up the following, requested by christos in ticket #271:
crypto/external/bsd/openssh/dist/ed25519-openssl.c up to 1.1.1.1
crypto/external/bsd/openssh/dist/ssherr-libcrypto.c up to 1.1.1.1
crypto/external/bsd/openssh/dist/ssherr-nolibcrypto.c up to 1.1.1.1
crypto/external/bsd/openssh/dist/hash.c delete
crypto/external/bsd/openssh/dist/PROTOCOL up to 1.26
crypto/external/bsd/openssh/dist/addr.c up to 1.9
crypto/external/bsd/openssh/dist/addr.h up to 1.1.1.4
crypto/external/bsd/openssh/dist/addrmatch.c up to 1.16
crypto/external/bsd/openssh/dist/auth-bsdauth.c up to 1.10
crypto/external/bsd/openssh/dist/auth-krb5.c up to 1.20
crypto/external/bsd/openssh/dist/auth.c up to 1.40
crypto/external/bsd/openssh/dist/auth.h up to 1.26
crypto/external/bsd/openssh/dist/auth2-chall.c up to 1.22
crypto/external/bsd/openssh/dist/auth2-gss.c up to 1.19
crypto/external/bsd/openssh/dist/auth2-hostbased.c up to 1.26
crypto/external/bsd/openssh/dist/auth2-pubkey.c up to 1.38
crypto/external/bsd/openssh/dist/auth2-pubkeyfile.c up to 1.5
[130 lines not shown]
Pull up the following, requested by christos in ticket #270:
external/public-domain/xz/dist/doc/examples/11_file_info.c up to 1.1.1.1
external/public-domain/xz/dist/po/pt_BR.gmo up to 1.1.1.1
external/public-domain/xz/dist/po/ca.gmo up to 1.1.1.1
external/public-domain/xz/dist/po/ca.po up to 1.1.1.1
external/public-domain/xz/dist/po/da.gmo up to 1.1.1.1
external/public-domain/xz/dist/po/da.po up to 1.1.1.1
external/public-domain/xz/dist/po/eo.gmo up to 1.1.1.1
external/public-domain/xz/dist/po/eo.po up to 1.1.1.1
external/public-domain/xz/dist/po/es.gmo up to 1.1.1.1
external/public-domain/xz/dist/po/es.po up to 1.1.1.1
external/public-domain/xz/dist/po/fi.gmo up to 1.1.1.1
external/public-domain/xz/dist/po/fi.po up to 1.1.1.1
external/public-domain/xz/dist/po/hr.gmo up to 1.1.1.1
external/public-domain/xz/dist/po/hr.po up to 1.1.1.1
external/public-domain/xz/dist/po/hu.gmo up to 1.1.1.1
external/public-domain/xz/dist/po/hu.po up to 1.1.1.1
external/public-domain/xz/dist/po/ka.gmo up to 1.1.1.1
[524 lines not shown]
Pull up the following, requested by christos in ticket #269:
external/mpl/bind//dist/bin/tests/convert_trs_to_junit.py up to
external/mpl/bind//dist/bin/tests/system/acl/ns2/named2.conf.j2 up to
external/mpl/bind//dist/bin/tests/system/acl/ns2/named3.conf.j2 up to
external/mpl/bind//dist/bin/tests/system/acl/ns2/named4.conf.j2 up to
external/mpl/bind//dist/bin/tests/system/acl/ns2/named5.conf.j2 up to
external/mpl/bind//dist/bin/tests/system/acl/ns2/named.conf.j2 up to
external/mpl/bind//dist/bin/tests/system/acl/ns3/named.conf.j2 up to
external/mpl/bind//dist/bin/tests/system/acl/ns4/named.conf.j2 up to
external/mpl/bind//dist/bin/tests/system/requirements.txt up to
external/mpl/bind//dist/bin/tests/system/re_compile_checker.py up to
external/mpl/bind//dist/bin/tests/system/ksr/ns1/named.conf.j2 up to
external/mpl/bind//dist/bin/tests/system/multisigner/ns3/named.conf.j2 up to
external/mpl/bind//dist/bin/tests/system/multisigner/ns4/named.conf.j2 up to
external/mpl/bind//dist/bin/tests/system/multisigner/ns5/named.conf.j2 up to
external/mpl/bind//dist/bin/tests/system/multisigner/tests_multisigner.py up to
external/mpl/bind//dist/bin/tests/system/proxy/ns1/named.conf.j2 up to
external/mpl/bind//dist/bin/tests/system/proxy/ns3/named.conf.j2 up to
[2260 lines not shown]
Pull up following revision(s) (requested by kre in ticket #267):
lib/libc/gen/sysctl.c: revision 1.40
lib/libc/gen/sysconf.3: revision 1.58
share/man/man7/sysctl.7: revision 1.172
lib/libc/time/localtime.c: revision 1.154
include/time.h: revision 1.57
PR lib/60219 -- Fix sysconf(_SC_TZNAME_MAX)
That value is supposed to be the minimum value allowed for
the maximum length of a timezone abbreviation. It cannot
be something larger than is allowed for that (and NAME_MAX
has nothing to do with it)
It defines the max lengths allowed for the words in
TZ=Frankenstein-7Monster-6[transition rules]
in old style POSIX TZ variable settings - the POSIX required
minimum value is 6 (so "Frankenstein" would not fit in a minimalist
[12 lines not shown]
Pull up following revision(s) (requested by kre in ticket #266):
external/bsd/top/dist/display.c: revision 1.11
external/bsd/top/dist/commands.c: revision 1.9
external/bsd/top/dist/machine/m_netbsd.c: revision 1.31
external/bsd/top/dist/utils.c: revision 1.7
external/bsd/top/dist/utils.c: revision 1.8
external/bsd/top/dist/utils.c: revision 1.9
<stype.h> "negative" char usage issue fixed.
sprintf/ctype police
Undo earlier meaningless change
Revert my botched change (rev 1.7, 2026-04-18 19:42:21 +0000) which
had the parens in the wrong place, which made it useless (pointed out
offlist by rillig@ - thanks). The change was made unnecessary by
christos later change (rev 1.8, 2026-04-18 21:37:04 +0000), so there
is no point fixing it, just make it go away.
Fix return value logic in pmap_changebit() (used to implement
pmap_clear_reference() and pmap_clear_modify()): We need to seed
the "combined_pte" with the mod/ref information stashed in the
vm_page because all of the mappings to the page may have already
been removed via pmap_page_protect(..., UVM_PROT_NONE), and we
need to use that "combined_pte" to return true if any of the bits
we've been asked to clear were set (previously we only returned
true if we actually cleared one from a mapping's PTE, which,
as previously noted, might all be gone by this point).
The symptom here would be random crashes under memory pressure,
things like spurious NULL-derefs, indicative of an anonymous
page being tossed under memory pressure and re-ZFOD'd, rather
than being sent to swap and properly paged back in.
Pull up following revision(s) (requested by isaki in ticket #1264):
sys/arch/x68k/x68k/disksubr.c: revision 1.38
usr.sbin/sysinst/arch/x68k/md.c: revision 1.14
sysinst/x68k: Remove unnecessary conditions in md_disklabe_is_default().
lp->d_bbsize and lp->d_sbsize should be constants (this is probably another
bug) and should not be part of this check.
Fix PR install/59600
x68k: Initialize d_bbsize and d_sbsize on the disklabel always.
These values are for (old) FFS, so it didn't make sense to initialize
only when the BSD disklabel was missing and the Human68k partition existed.
This avoids disklabel(8)'s warnings:
disklabel: boot block size 0
disklabel: super block size 0
Inspired from PR install/59600.
Pull up following revision(s) (requested by isaki in ticket #265):
sys/arch/x68k/x68k/disksubr.c: revision 1.38
usr.sbin/sysinst/arch/x68k/md.c: revision 1.14
sysinst/x68k: Remove unnecessary conditions in md_disklabe_is_default().
lp->d_bbsize and lp->d_sbsize should be constants (this is probably another
bug) and should not be part of this check.
Fix PR install/59600
x68k: Initialize d_bbsize and d_sbsize on the disklabel always.
These values are for (old) FFS, so it didn't make sense to initialize
only when the BSD disklabel was missing and the Human68k partition existed.
This avoids disklabel(8)'s warnings:
disklabel: boot block size 0
disklabel: super block size 0
Inspired from PR install/59600.
Pull up following revision(s) (requested by riastradh in ticket #264):
sys/dev/nvmm/x86/nvmm_x86_svm.c: revision 1.94
sys/dev/nvmm/x86/nvmm_x86_vmx.c: revision 1.94
nvmm: Don't report physical lapic freq as virtual lapic freq.
The virtual lapic emulated by qemu in software always ticks at 1 GHz,
but the physical lapic on my laptop, for example, ticks at 24 MHz.
In order for this to work as iMil intended, we need some way for the
hypervisor (such as qemu) to tell nvmm what its lapic frequency is.
Until we have that, we can't correctly report any alleged lapic
frequency to the guest.
PR kern/59424: hardclock ticks run at breakneck pace under qemu
Pull up following revision(s) (requested by andvar in ticket #2011):
sys/dev/pci/ahcisata_pci.c: revision 1.73
ahcisata(4): disable NCQ for VIA VT8251 integrated SATA controller.
NCQ support is known to be non-compliant or broken on this chipset,
causing timeouts and instability.
The issue is reproducible in NetBSD using 'smartctl -a`.
The workaround is to disable NCQ, which has already been done in other
OS drivers.
Pull up following revision(s) (requested by andvar in ticket #1263):
sys/dev/pci/ahcisata_pci.c: revision 1.73
ahcisata(4): disable NCQ for VIA VT8251 integrated SATA controller.
NCQ support is known to be non-compliant or broken on this chipset,
causing timeouts and instability.
The issue is reproducible in NetBSD using 'smartctl -a`.
The workaround is to disable NCQ, which has already been done in other
OS drivers.
Pull up following revision(s) (requested by andvar in ticket #263):
sys/dev/pci/ahcisata_pci.c: revision 1.73
ahcisata(4): disable NCQ for VIA VT8251 integrated SATA controller.
NCQ support is known to be non-compliant or broken on this chipset,
causing timeouts and instability.
The issue is reproducible in NetBSD using 'smartctl -a`.
The workaround is to disable NCQ, which has already been done in other
OS drivers.
Pull up the following, requested by kre in ticket #261:
external/public-domain/tz/dist/NEWS up to 1.7
external/public-domain/tz/dist/TZDATA_VERSION up to 1.45
external/public-domain/tz/dist/northamerica up to 1.6
external/public-domain/tz/dist/version up to 1.18
external/public-domain/tz/dist/zone.tab up to 1.5
external/public-domain/tz/dist/zone1970.tab up to 1.6
external/public-domain/tz/dist/zonenow.tab up to 1.7
Update to tzdata2026bgtz
from
https://github.com/JodaOrg/global-tz/releases/download/2026bgtz/tzdata2026bgtz.tar.gz
One change of note:
British Columbia moved to permanent -07 on 2026-03-09.
Pull up following revision(s) (requested by hans in ticket #1261):
sys/dev/dec/dzkbd.c: revision 1.34
dzkbd: set the keyboard type according to what lk201_init() detected
This makes wsconsctl report the correct keyboard type. The layout is
still hardcoded for a LK401 by default, though.
