fetch G_CPP20_SOURCES.

(mrg)

Fix format specifier for physmem from %d to 0x%"PRIxPSIZE" in multiple places.

Should fix VERBOSE_INIT_ARM for various evbarm kernel configs.
Also add 0x prefix in few previously fixed places to improve readability.

(andvar)

tests/snprintb: test '=' and '*' directives that can never match

(rillig)

snprintb.3: sync examples with reality

(rillig)

snprintb_m: limit length of generated strings

The manual page promises that the 'max' argument limits the length of
the generated strings, so don't generate any strings that are longer
than that limit. Mark incomplete strings with a trailing '#' to make
them easily recognizable.

(rillig)

tests/snprintb: fix out-of-bounds memory read (since 2024-02-16)

Before t_snprintb.c 1.20, the buffer size was required to be greater
than zero. Allowing the buffer size to be zero led to buf[-1] being
checked. On amd64, that byte happened to be 0, on i386 it didn't.

Fixes PR lib/57951.

(rillig)

add missing chunk for repro-build. fix gcc warnings.

(christos)

play the same lazy cursor (un)draw trick as cgsix and friends
visible speedup in things like systat

(macallan)

fix debug sets for sun2 (libgcc_s_g.a and libgcc_eh_g.a should be in shl.mi)

(christos)

Updates for less - add me as co-maintainer, update to latest version.

(simonb)

enable glyph cache, anti-aliased fonts etc.

(macallan)

remove check for unused bits in attr2idx() - this really wasn't helpful

(macallan)

fenv(3): Fix fetestexcept to avoid side effects on trap state.

PR port-amd64/57949

(riastradh)

fix typo in comment

(uwe)

snprintb: fix how named bit-fields are split into multiple lines

(rillig)

tests/snprintb: add more tests, especially for snprintb_m

(rillig)

fenv(3): Add test for PR port-amd64/57949.

(riastradh)

Add a hook that adds more libraries after PROGDPLIBS

(christos)

fix static build

(christos)

remove unintended printf() in previous.  (thx dh)

(mrg)

longjmp(3) t_sigstack: Fix fencepost error.

Extremely unlikely to cause trouble, but let's just turn that into
`never' to keep it easier for readers.

PR lib/57946

(riastradh)

ramdisk-zfsroot: Enable build by default on amd64.

XXX Should maybe copy this to other ports like evbarm64 too.

PR port-amd64/57948

(riastradh)

ciss(4): Fix panic when the number of logical drive is zero.

Currently, this drives requires at least one logical drive.
If there is no any logical volume, don't attach the driver.

(msaitoh)

longjmp(3) t_sigstack: Use a sigaltstack per handler entry.

longjmp evidently doesn't reset the state of whether the process is
executing on the alternate signal stack.  So when we re-enter the
signal handler, the alternate stack appears to be still in use, and
the system chooses the original stack for the second call to the
signal handler -- which trips our assertion asking to verify that the
signal handler is always using an alternate stack.

Not strictly necessary for the signal handler to use an alternate
stack on re-entry, but this makes it clearer that the signal handler
itself is always using the alternate stack so we can verify that the
interrupted code is _not_ in the signal handler.

With this change, the test now passes on aarch64.

PR lib/57946

(riastradh)

longjmp(3) t_sigstack: Note aarch64 seems to DTRT.

But only by code inspection; it appears to have another problem: on
re-entry, the signal handler is called on the normal stack, not on
the alternate signal stack.

PR lib/57946

(riastradh)

longjmp(3) t_sigstack: Print which entry failed.

PR lib/57946

(riastradh)

longjmp(3): Test signal mask vs stack restore with siglongjmp too.

PR lib/57946

(riastradh)

make TSC get a quality of -100 on AMD Family 15h and 16h

this should "fix" PR#56322 and is known as AMD errata
"778: Processor Core Time Stamp Counters May Experience Drift"

(mrg)

Ticket #1800

(martin)

Pull up following revision(s) (requested by tsutsui in ticket #1800):

sys/arch/vax/vsa/vsbus.c: revision 1.69 (patch)
sys/arch/vax/vsa/ncr.c: revision 1.52

Fix SCSI tranfer corruption on VAXstation 3100/m30 (KA420) on netboot.

See my post on port-vax@ for details:
https://mail-index.netbsd.org/port-vax/2024/02/16/msg004866.html
and "go ahead!" from ragge@.

(martin)

Ticket #601

(martin)

Pull up following revision(s) (requested by tsutsui in ticket #601):

sys/arch/vax/vsa/vsbus.c: revision 1.69
sys/arch/vax/vsa/ncr.c: revision 1.52

Fix SCSI tranfer corruption on VAXstation 3100/m30 (KA420) on netboot.

See my post on port-vax@ for details:
https://mail-index.netbsd.org/port-vax/2024/02/16/msg004866.html
and "go ahead!" from ragge@.

(martin)

longjmp(3): Paranoia: more error checking in PR lib/57946 test.

(riastradh)

longjmp(3): Add test for PR lib/57946.

(riastradh)

default is now 16K

(christos)

ftp: bump FTPBUFLEN from 4kB to 16kB

sourceforge.net returns a 5kB content-security-policy.
Analyzed by mlelstv@ who reports usual limits are between 4kB and 48kB.

(wiz)

Add -b <buflen> to specify the buffer size.

(christos)

Disentangle dhcp from bind by putting enough of bind 9.16.42 for it to build
here. Bind keeps removing the bits that dhcp uses to build and keeping bind
up-to-date and dhcp building is a losing battle.

(christos)

getconf.1: Note that leading underscores in configuration
variable names are ignored by getconf(1).

While here, add a section with examples, and make the synopsis
more concise.

PR bin/57875

(jkoshy)

Add an options pretty-printer, pass some lint.

(christos)

PR/57945: Jan-Benedict Glaw: makefs: msdos filesystems with label not
reproducible.
When we specify a label, the volume label is used to create the root dir
and it gets stamped by the timestamp. We were trying to set the timestamp
in the fs-specific part of the options parsing which did not work since
the method was called only for fs_specific options. Move setting of the
timestamp just before we create the fs, where we reconcile the rest of
the options.

(christos)

mman.h: fix snprintb description for alignment 2^60

(rillig)

Tickets #589 - #593, #595 - #600

(martin)

Ticket #1799

(martin)

Pull up following revision(s) (requested by tsutsui in ticket #1799):

sys/dev/tc/zskbd.c: revision 1.22

Fix another fatal typo that causes zskbd_cngetc() to stall as dzkbd.
Tested on my DEC 3000/300 and LK421.

(martin)

Pull up following revision(s) (requested by tsutsui in ticket #600):

sys/dev/tc/zskbd.c: revision 1.22

Fix another fatal typo that causes zskbd_cngetc() to stall as dzkbd.
Tested on my DEC 3000/300 and LK421.

(martin)

Pull up following revision(s) (requested by skrll in ticket #599):

sys/arch/arm/broadcom/bcm53xx_eth.c: revision 1.44

Test sc->sc_soft_ih (not sc->sc_ih) to see if the soft interrupt got
established correctly.

From Mori Hiroki.

Fix some error recovery while I'm here.

(martin)

Pull up following revision(s) (requested by skrll in ticket #597):

sys/arch/evbarm/conf/std.bcm53xx: revision 1.21
sys/arch/arm/broadcom/bcm53xx_eth.c: revision 1.43
sys/arch/arm/broadcom/bcm53xx_pax.c: revision 1.23

Define KERNEL_VOFFSET_RUNTIME=1 to fix build of BCM5301X and BCM56340

Fix non-DIAGNOSTIC build

(martin)

Revert this part:

strftime %s now uses tm_gmtoff if available.  (Problem and draft
patch reported by Dag-Erling Sm淡rgrav.)

of the tzcode2924a update.  It is bogus.  The "problem" is/was a simple
misunderstanding of what strftime(%s) is intended to output.  The "fix"
breaks it.

(kre)

if we're building with GCC and MACHINE_CPU is aarch64, error out since
that isn't going to work.

doing this better in config(1) is difficult, but at least we can
detect and give a useful error message for this case instead of just
erroring out with some compiler options aren't supported.  if we have
a good solution for config(1) we can remove this hack here..

might want to copy this hack for riscv too.

(mrg)

Change KDB to KGDB, including "sys/kgdb.h", which were likely meant to be defined.

Also comment out kgdb_machdep.c in files.aarch64, it doesn't exist yet.

(andvar)

Ensure that the size of the stack is properly specified (2*USPACE) so it matches the allocation of stack pages done in pmap_bootstrap(). If this is not properly in sync, then the stack pointer may end up in the redzone right before the stack causing mmu faults. This issue has been observed on a T2000 (sun4v) system while probing the devices (pci/ebus/com) during bootstrap

(palle)

new unbound

(christos)

bump libunbound

(christos)

merge differences between 1.16.3 and 1.19.1

(christos)

new nsd

(christos)

merge differences between nsd-4.6.0 and nsd-4.8.0

(christos)

Fix SCSI tranfer corruption on VAXstation 3100/m30 (KA420) on netboot.

See my post on port-vax@ for details:
https://mail-index.netbsd.org/port-vax/2024/02/16/msg004866.html
and "go ahead!" from ragge@.  Should be pulled up to netbsd-10 and -9.

(tsutsui)

Ticket #1798

(martin)

Pull up following revision(s) (requested by tsutsui in ticket #1798):

sys/dev/dec/dzkbd.c: revision 1.32
sys/dev/dec/lk201var.h: revision 1.8
sys/dev/dec/lk201_ws.c: revision 1.11

Fix a fatal typo that causes dzkbd_cngetc() to stall.

Use proper macro for return values and remove #if 0'ed out block.
Mostly from OpenBSD/vax. No binary changes.

(martin)

Pull up following revision(s) (requested by tsutsui in ticket #596):

sys/dev/dec/dzkbd.c: revision 1.32
sys/dev/dec/lk201var.h: revision 1.8
sys/dev/dec/lk201_ws.c: revision 1.11

Fix a fatal typo that causes dzkbd_cngetc() to stall.

Use proper macro for return values and remove #if 0'ed out block.
Mostly from OpenBSD/vax. No binary changes.

(martin)

Tickets #1935 and #1936

(martin)

Pull up following revision(s) (requested by shm in ticket #1936):

libexec/utmp_update/utmp_update.c: revision 1.14

Check for non-printable characters in ut_host.

(martin)

Tickets #1796 and #1797

(martin)

Pull up following revision(s) (requested by shm in ticket #1797):

libexec/utmp_update/utmp_update.c: revision 1.14

Check for non-printable characters in ut_host.

(martin)

Pull up following revision(s) (requested by shm in ticket #595):

libexec/utmp_update/utmp_update.c: revision 1.14

Check for non-printable characters in ut_host.

(martin)

Pull up following revision(s) (requested by macallan in ticket #593):

sys/dev/ic/sti.c: revision 1.32

Make this work properly on PCI Visualize EG:
- use bus_space_*_stream() for all register accesses in order to avoid
  byte order conversion on PCI devices
- when switching to framebuffer mode, request as many text planes as STI allows
- request access to both text and non-text planes in fb mode

With this and the bus_space commit a few days ago I have usable X on my C360
and a PCI Visualize EG.

This needs testing on quite literally everything else.

(martin)

Pull up following revision(s) (requested by macallan in ticket #592):

sys/arch/hppa/hppa/mainbus.c: revision 1.13
sys/arch/hppa/dev/elroy.c: revision 1.7
sys/arch/hppa/dev/dino.c: revision 1.17
sys/arch/hppa/include/bus_funcs.h: revision 1.2
sys/arch/hppa/include/bus_defs.h: revision 1.3

add missing bus_space_*_stream() methods instead of quietly aliasing them
to their potentially byte-swapping regular counterparts

ok skrll@

(martin)

Pull up following revision(s) (requested by markd in ticket #591):

external/bsd/blocklist/bin/blocklistd.conf.5: revision 1.3
external/bsd/blocklist/bin/conf.c: revision 1.4
external/bsd/blocklist/bin/conf.c: revision 1.5
external/bsd/blocklist/bin/conf.c: revision 1.6
external/bsd/blocklist/etc/blocklistd.conf: revision 1.3

PR/57905: Mark Davies: blocklistd fails to parse ipv6 addresses.
fix typo

PR/57905: Mark Davies: handle empty string.

add an IPv6 example to blocklistd.conf(5)

add an IPv6 example to blocklistd.conf example file

(martin)

Pull up the following, requested by kre in ticket #1935:

external/public-domain/tz/dist/Makefile        up to 1.1.1.38
external/public-domain/tz/dist/NEWS            up to 1.1.1.45
external/public-domain/tz/dist/TZDATA_VERSION  up to 1.37
external/public-domain/tz/dist/africa          up to 1.1.1.33
external/public-domain/tz/dist/asia            up to 1.12
external/public-domain/tz/dist/australasia      up to 1.9
external/public-domain/tz/dist/checknow.awk    up to 1.1.1.2
external/public-domain/tz/dist/etcetera        up to 1.1.1.8
external/public-domain/tz/dist/europe          up to 1.1.1.39
external/public-domain/tz/dist/leap-seconds.list up to 1.7
external/public-domain/tz/dist/leapseconds      up to 1.7
external/public-domain/tz/dist/leapseconds.awk  up to 1.1.1.14
external/public-domain/tz/dist/northamerica    up to 1.1.1.35
external/public-domain/tz/dist/southamerica    up to 1.1.1.25
external/public-domain/tz/dist/theory.html      up to 1.1.1.19
external/public-domain/tz/dist/version          up to 1.12
external/public-domain/tz/dist/zishrink.awk    up to 1.1.1.9
external/public-domain/tz/dist/zonenow.tab      up to 1.1.1.2
doc/3RDPARTY apply patch

Updated tzdata to 2024a

(martin)

Pull up following revision(s) (requested by hans in ticket #590):

sys/arch/vax/vax/machdep.c: revision 1.197

Include leds.h to make /dev/leds work.

(martin)

PR 57941: remove duplciate declaration (copy+pasto)

(martin)

Fix MKREPRO build (Jan-Benedict Glaw)

(christos)

Fix MKREPRO build (Jan-Benedict Glaw)

(christos)

Mention tzcode2024a

(christos)

Sync with tzcode2024a:
Release 2024a - 2024-02-01 09:28:56 -0800

  Changes to code

    The FROM and TO columns of Rule lines can no longer be "minimum"
    or an abbreviation of "minimum", because TZif files do not support
    DST rules that extend into the indefinite past - although these
    rules were supported when TZif files had only 32-bit data, this
    stopped working when 64-bit TZif files were introduced in 1995.
    This should not be a problem for realistic data, since DST was
    first used in the 20th century.  As a transition aid, FROM columns
    like "minimum" are now diagnosed and then treated as if they were
    the year 1900; this should suffice for TZif files on old systems
    with only 32-bit time_t, and it is more compatible with bugs in
    2023c-and-earlier localtime.c.  (Problem reported by Yoshito
    Umaoka.)

    localtime and related functions no longer mishandle some
    timestamps that occur about 400 years after a switch to a time
    zone with a DST schedule.  In 2023d data this problem was visible
    for some timestamps in November 2422, November 2822, etc. in
    America/Ciudad_Juarez.  (Problem reported by Gilmore Davidson.)

    strftime %s now uses tm_gmtoff if available.  (Problem and draft
    patch reported by Dag-Erling Sm淡rgrav.)

  Changes to build procedure

    The leap-seconds.list file is now copied from the IERS instead of
    from its downstream counterpart at NIST, as the IERS version is
    now in the public domain too and tends to be more up-to-date.
    (Thanks to Martin Burnicki for liaisoning with the IERS.)

  Changes to documentation

    The strftime man page documents which struct tm members affect
    which conversion specs, and that tzset is called.  (Problems
    reported by Robert Elz and Steve Summit.)

(christos)

Pullup the following, requested by kre in ticket #1796:

external/public-domain/tz/dist/Makefile        up to 1.1.1.38
external/public-domain/tz/dist/NEWS            up to 1.1.1.45
external/public-domain/tz/dist/TZDATA_VERSION  up to 1.37
external/public-domain/tz/dist/africa          up to 1.1.1.33
external/public-domain/tz/dist/asia            up to 1.12
external/public-domain/tz/dist/australasia      up to 1.9
external/public-domain/tz/dist/checknow.awk    up to 1.1.1.2
external/public-domain/tz/dist/etcetera        up to 1.1.1.8
external/public-domain/tz/dist/europe          up to 1.1.1.39
external/public-domain/tz/dist/leap-seconds.list up to 1.7
external/public-domain/tz/dist/leapseconds      up to 1.7
external/public-domain/tz/dist/leapseconds.awk  up to 1.1.1.14
external/public-domain/tz/dist/northamerica    up to 1.1.1.35
external/public-domain/tz/dist/southamerica    up to 1.1.1.25
external/public-domain/tz/dist/theory.html      up to 1.1.1.19
external/public-domain/tz/dist/version          up to 1.12
external/public-domain/tz/dist/zishrink.awk    up to 1.1.1.9
external/public-domain/tz/dist/zonenow.tab      up to 1.1.1.2
doc/3RDPARTY apply patch

Updated tzdata to 2024a

(martin)

Pull up following revision(s) (requested by gutteridge in ticket #589):

sys/dev/usb/ehci.c: revision 1.322
sys/dev/usb/ehcireg.h: revision 1.39

avoid different struct type problem.

(martin)

snprintb: convert macros to local functions

Let the compiler decide whether to inline the functions; allow stepping
through the code in a debugger.

(rillig)

Whitespace.

(mlelstv)

Steal the sync operation descriptions from FreeBSD and improve other
wording in this area.

Inspired by jmcneill@

(skrll)

Fix another fatal typo that causes zskbd_cngetc() to stall as dzkbd.

Tested on my DEC 3000/300 and LK421.
Should be pulled up to netbsd-10 and netbsd-9.

XXX: sys/arch/vax/uba/qvkbd.c seems missed in the following lk201 changes:
https://mail-index.netbsd.org/source-changes/2015/01/02/msg062024.html

(tsutsui)

getnameinfo(3): fix/prettify markup

(uwe)

Replace obsolete pv_dump() call with pmap_db_mdpg_print().

It was rewritten on rev 1.107, but not replaced with new implementation in
PMAP_PV_DEBUG guarded block.

(andvar)

snprintb: do not modify bufsize when producing multiple lines

(rillig)

snprintb: eliminate two local variables, allow zero-size buffer

Like snprintf, the buffer size may be zero. Unlike snprintf, the buffer
must not be NULL.

(rillig)

Remove obsolete code.

Per src/doc/CHANGES.prev support for the NI_WITHSCOPEID flag was removed
in NetBSD 1.6.

(jkoshy)

snprintb: use size_t for buffer sizes and positions

(rillig)

snprintb: fix integer overflow when writing past a small buffer

Previously, snprintb returned -1 in this case, assuming that the
snprintf used in FMTSTR validates against an overly large buffer size.

(rillig)

snprintb: use unsigned integers for parsing the bitfmt

(rillig)

tests/snprintb: fix test for 8-bit field value

The previous version tested the behavior on a platform with signed
'char' before the portability fix.

(rillig)

snprintb: fix '=' and ':' for 8-bit values on platforms with signed char

Previously, '=' and ':' worked only on platforms where plain 'char' is
unsigned. On platforms where plain 'char' is signed, only 7-bit values
worked.

(rillig)

snprintb: eliminate a few local variables

(rillig)

snprintb: rename local variables

The single-letter variables 't', 's', 'l' and 'c' were too hard to
decipher.

The variable 'f_len' was used for two independent purposes.

Use a narrow scope for some variables, to avoid having to keep track of
22 individual variables at the same time.

No binary change.

(rillig)

Fix closing bracket for strdisasm() function.

Fixes KOBJ_MACHDEP_DEBUG enabled build for aarch64.

(andvar)

Retire BCM53XX_CONSOLE_EARLY in favour of EARLYCONS

(skrll)

Test sc->sc_soft_ih (not sc->sc_ih) to see if the soft interrupt got
established correctly.

From Mori Hiroki.

Fix some error recovery while I'm here.

(skrll)

Trailing whitespace

(skrll)

Trailing whitespace

(skrll)

Fix non-DIAGNOSTIC build

(skrll)

Trailing whitespace

(skrll)

Trailing whitespace

(skrll)

Note that the NI_WITHSCOPEID flag is obsolete.

(jkoshy)

snprintb: clean up

Remove redundant parentheses and casts.

Indent statement-like macros consistently, use separate lines for each
statement, add parentheses to macro definitions.

Remove CONSTCOND comments as lint doesn't need them anymore.

No binary change.

(rillig)

tests/snprintb: clean up existing tests, add more tests

Due to the check that any bytes beyond the expected output must be
unmodified, there's no need anymore to explicitly write the "ZZZ" at the
end of the expected output. While here, remove the redundant trailing
"\0".

Add more tests to cover possible situations where an out-of-bounds write
may have occurred. In some cases, the line length specified in
snprintb_m is exceeded.

(rillig)

snprintb: fix string termination (since today)

In the previous commit, I had accidentally only run the tests for
snprintb_m but not those for snprintb, thereby missing a newly
introduced bug that would not null-terminate the resulting strings.

Add more tests to cover similar situations in which the buffer is too
small to contain the complete output.

(rillig)

snprintb: rename buflen to bufsize, following the wording in snprintf

(rillig)

snprintb: fix out-of-bounds write

(rillig)

blitter time!
everything except drawing characters i now done by hardware
next step - glyphcache

(macallan)

Document the NI_NUMERICSCOPE flag.

PR lib/57832

(jkoshy)

tests/libutil/snprintb_m: add tests for small line length

(rillig)

doc: Fix syntax

(nia)

sprinkle unused.

(christos)

Change entry for #594

(sborrill)

Ticket #594

(sborrill)

Pull up the following revisions(s) (requested by martin in ticket #594):
usr.sbin/sysinst/label.c: revision 1.51

PR 57927: when comparing old and new partition state during renumbering,
ignore differences in the install target flag - the backend might have
flipped it off already to ensure only a single partition is marked
as install target.

(sborrill)

PR 57927: when comparing old and new partition state during renumbering,
ignore differences in the install target flag - the backend might have
flipped it off already to ensure only a single partition is marked
as install target.

(martin)

Use proper macro for return values and remove #if 0'ed out block.

Mostly from OpenBSD/vax. No binary changes.

(tsutsui)

Fix a fatal typo that causes dzkbd_cngetc() to stall.

Should be pulled up to netbsd-10 and netbsd-9.

(tsutsui)

s/Enque/Enqueue/ in comment.

(andvar)

s/enqueing/enqueuing/ in debug messages (took a bait from recent Nick's commit)
s/occaision/occasion/ in comment.

(andvar)

Define KERNEL_VOFFSET_RUNTIME=1 to fix build of BCM5301X and BCM56340

(skrll)

https://www.phoronix.com/news/IWD-WPA-WiFi-Auth-Vulns
https://www.top10vpn.com/research/wifi-vulnerabilities/

PEAP client: Update Phase 2 authentication requirements

The previous PEAP client behavior allowed the server to skip Phase 2
authentication with the expectation that the server was authenticated
during Phase 1 through TLS server certificate validation. Various PEAP
specifications are not exactly clear on what the behavior on this front
is supposed to be and as such, this ended up being more flexible than
the TTLS/FAST/TEAP cases. However, this is not really ideal when
unfortunately common misconfiguration of PEAP is used in deployed
devices where the server trust root (ca_cert) is not configured or the
user has an easy option for allowing this validation step to be skipped.

Change the default PEAP client behavior to be to require Phase 2
authentication to be successfully completed for cases where TLS session
resumption is not used and the client certificate has not been
configured. Those two exceptions are the main cases where a deployed
authentication server might skip Phase 2 and as such, where a more
strict default behavior could result in undesired interoperability
issues. Requiring Phase 2 authentication will end up disabling TLS
session resumption automatically to avoid interoperability issues.

Allow Phase 2 authentication behavior to be configured with a new phase1
configuration parameter option:
'phase2_auth' option can be used to control Phase 2 (i.e., within TLS
tunnel) behavior for PEAP:
* 0 = do not require Phase 2 authentication
* 1 = require Phase 2 authentication when client certificate
  (private_key/client_cert) is no used and TLS session resumption was
  not used (default)
* 2 = require Phase 2 authentication in all cases

(christos)

Allow overriding the language standard to something newer.

(christos)

Mention bind security patches

(christos)

make things compile again.

(christos)

doc: Changes since 20/01

(nia)

Apply patch for CVE-2023-50387 and CVE-2023-50868:

No public information has been posted (that I can find)

(christos)

Apply patch for CVE-2023-6516:

To keep its cache database efficient, `named` running as a recursive
resolver occasionally attempts to clean up the database. It uses
several methods, including some that are asynchronous: a small
chunk of memory pointing to the cache element that can be cleaned
up is first allocated and then queued for later processing. It was
discovered that if the resolver is continuously processing query
patterns triggering this type of cache-database maintenance, `named`
may not be able to handle the cleanup events in a timely manner.
This in turn enables the list of queued cleanup events to grow
infinitely large over time, allowing the configured `max-cache-size`
limit to be significantly exceeded. This issue affects BIND 9
versions 9.16.0 through 9.16.45 and 9.16.8-S1 through 9.16.45-S1.

(christos)

Apply patch for CVE-2023-5679:

A bad interaction between DNS64 and serve-stale may cause `named`
to crash with an assertion failure during recursive resolution,
when both of these features are enabled. This issue affects BIND
9 versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0
through 9.19.19, 9.16.12-S1 through 9.16.45-S1, and 9.18.11-S1
through 9.18.21-S1.

(christos)

Apply patch for CVE-2023-5517:

A flaw in query-handling code can cause `named` to exit prematurely
with an assertion failure when: - `nxdomain-redirect <domain>;` is
configured, and - the resolver receives a PTR query for an RFC 1918
address that would normally result in an authoritative NXDOMAIN
response. This issue affects BIND 9 versions 9.12.0 through 9.16.45,
9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.8-S1 through
9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.

(christos)

Apply patch for CVE-2023-4408:

The DNS message parsing code in `named` includes a section whose
computational complexity is overly high. It does not cause problems
for typical DNS traffic, but crafted queries and responses may
cause excessive CPU load on the affected `named` instance by
exploiting this flaw. This issue affects both authoritative servers
and recursive resolvers. This issue affects BIND 9 versions 9.0.0
through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19,
9.9.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.45-S1, and
9.18.11-S1 through 9.18.21-S1.

(christos)

mfii(4): Apply two changes from OpenBSD to fix an unknown firmware state.

My own MegaRAID 946N-8i 2G", firmware 50.5.0-2594 failed to attach.

mfii0: unknown firmware state 1879048192

1879048192 equals to 0x70000000(== MFI_STATE_FW_INIT_2).
Apply following two OpenBSD commits to resolve this problem.

----------------------------
sys/dev/pci/mfii.c OpenBSD rev. 1.86
sys/dev/ic/mfireg.h OpenBSD rev. 1.52

Make mfii(4) recover from firmware FAULT state on startup.

In case firmware initially comes up in FAULT state, reset the device and
give it one more chance to attach successfully. The Linux megaraid_sas
driver applies the same workaround in this case. There seems to be a bug
in some firmware versions which can trigger this behaviour; see mainline
Linux commit 6431f5d7c6025f8b007af06ea090de308f7e6881

Problem observed by me with mfii(4) attached via KVM PCI-passthrough:
mfii0 at pci0 dev 2 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: msi
mfii0: firmware fault

With this workaround in place, attachment succeeds and the device works:
mfii0 at pci0 dev 2 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: msi
mfii0: firmware fault; attempting full device reset, this can take some time
mfii0: "RAID Ctrl SAS 6G 1GB (D3116C)", firmware 23.29.0-0019, 1024MB cache

Tested for regressions on bare metal by Hrvoje with two different adapters:
mfii0 at pci1 dev 0 function 0 "Symbios Logic MegaRAID SAS3508" rev 0x01: msi
mfii0: "PERC H740P Mini ", firmware 51.16.0-4076, 8192MB cache
mfii0 at pci4 dev 0 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: msi
mfii0: "ServeRAID M5110", firmware 23.34.0-0023, 512MB cache

ok jmatthew@

----------------------------
sys/dev/pci/mfii.c OpenBSD rev. 1.87

Give mfii(4) firmware more time to transition out of UNDEFINED state.

Prevents occasional failure to recover from firmware FAULT state where
the driver gave up too early: mfii0: firmware stuck in state 0

ok deraadt@

(msaitoh)

Add the Sun3 obio flavor's DMA controller access registers.

(thorpej)

crude beginning of a native driver for PCI Visualize EG cards
so far it supports:
- colour
- virtual consoles
todo:
- mmap
- hardware acceleration
- STI refactoring

(macallan)

in sti_screen_setup() don't bother looking for fonts if STI_FBMODE is requested

(macallan)

Move sireg.h from vme/ to sun/ -- the same (or nearly so) register defns
are used by multiple bus attachments.

(thorpej)

ktrace.1: apply minor spelling consistency

Use "tracepoint" consistently, rather than a mix with "trace point",
sometimes in the same paragraph. "Breakpoint" and "tracepoint" are
most commonly rendered without the space in tech documentation, AFAIK.

(gutteridge)

Quote argument to -n as required. [ -n ] is not a syntax error but
evaluates to true.

(mlelstv)

Fix typo in error message.

(isaki)

PR/57925: Jan-Benedict Glaw: Honor $MKREPRO_TIMESTAMP, don't embed name and
stamp in gzip.

(christos)

put quotes back

(christos)

PR/57924: Jan-Benedict Glaw: Use $MKREPRO_TIMESTAMP for mkubootimage

(christos)

PR/57923: Jan-Benedict Glaw: Use $MKREPRO_TIMESTAMP for mkubootimage

(christos)

make kqfilter() behave the same for PIPE_SOCKETPAIR pipe as it does
for standard one - refuse EVFILT_WRITE if the reader is already disconnected

fixes test failure for kernel/kqueue/write/t_pipe.c on PIPE_SOCKETPAIR kernel

PR kern/55690

(jdolecek)

Fix spello in debug output

(skrll)