mount_lfs(8): Add unreachable() to fix clang build.
dependall ===> sbin/mount_lfs
/home/source/ab/HEAD-llvm/src/sbin/mount_lfs/mount_lfs.c:319:1: error: function declared 'noreturn' should not return [-Werror,-Winvalid-noreturn]
The only two cases in invoke_cleaner are already handled, so the rest
should be unreachable.
Import bind-9-20-27 (Previous was bind-9-20-24)
iNotes for BIND 9.20.27#
New Features#
Disclose active Negative Trust Anchors with Extended DNS Error 33.
A Negative Trust Anchor (RFC 7646) turns off DNSSEC validation for a
domain, so a name that would normally fail validation resolves instead. named
now marks such answers with Extended DNS Error code 33, "Negative Trust
Anchor", so operators can see at a glance when a response came back only
because an NTA was in effect. [GL #6268]
Feature Changes#
Speed up RPZ policy zone updates.
RPZ updates used to be applied one small step at a time, adding overhead on
large policy zones. Updates are now applied as a single batch, improving
update performance for large RPZ zones, at the cost of no longer overlapping
with concurrent updates. [GL #5787] [GL #6270]
Bug Fixes#
Ensure NSEC authority does not cross zonecut boundary.
When using a cached NSEC record to prove that a delegation is insecure, named
[239 lines not shown]
ptrace(2): Fix compat32 register set types in previous.
Not always `struct reg32' or `struct fpreg32', notably on arm32 --
make sure to say `process_reg32'/`process_fpreg32'/`process_dbreg32'.
(Here `compat32' means oabi?)
Followups for:
PR port-amd64/60556: panic in process_read_fpregs_xmm
PR kern/60595: System lockup using gdb(1) on kernel with
DEBUG+LOCKDEBUG
PR kern/60658: netbsd32_process_read_dbregs() needs the same fix as
native amd64 process_read_dbregs()
don't expose us to userland until things are fully initialized.
Same class of bugs that run(4) had in other USB drivers.
PR kern/60665: run: hot-plugging USB wifi crashes due to use of if_attach
run: don't expose us to userland until things are fully initialized.
Fixes crash seen when hot-plugging run(4) with a running wpa_supplicant.
PR kern/60665: run: hot-plugging USB wifi crashes due to use of if_attach
Mark inode modified in lfs_putpages, when there are dirty pages.
This ensures the inode is written after the pages, avoiding a situation
that manifests as files mysteriously reverted (often to zero length)
and "SEGMENT %d CLAIMS %d BYTES BUT HAS %d (HIGH BY %d)" errors from fsck_lfs
pass 5.
sun4v: Add xhci(4) to sparc64 GENERIC config.
Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller is
present in SPARC S7-2 servers (device id 0x8241).
Not tested yet.
Sort the list of segments entered with -s so they appear in the output in
sequence regardless of the input order. In particular, the old code always
produced the segments in reverse order.
ptrace(2): Tidy register access: no sketchy function pointer casts.
Followups for:
PR port-amd64/60556: panic in process_read_fpregs_xmm
PR kern/60595: System lockup using gdb(1) on kernel with
DEBUG+LOCKDEBUG
PR kern/60658: netbsd32_process_read_dbregs() needs the same fix as
native amd64 process_read_dbregs()
netbsd32_ptrace: Fix locking around ptrace register access.
PR kern/60658: netbsd32_process_read_dbregs() needs the same fix as
native amd64 process_read_dbregs()
sys/param.h: Welcome to 11.99.8, courtsey of struct proc reordering.
PR kern/60653: posix_spawn(3) causes incorrect stack base information
XXX kernel ABI revbump -- NOT FOR PULLUP
struct proc: Put p_stackbase in the [p_startcopy,p_endcopy) range.
It is inherited by the child because the child has exactly the same
memory layout as the parent.
Cleanup after:
PR kern/60653: posix_spawn(3) causes incorrect stack base information
XXX kernel ABI revbump -- NOT FOR PULLUP
fork(2), vfork(2): Copy the parent's stack base pointer to the child.
Don't just leak whatever random stack pointer some recycled struct
proc had!
TBD: Move p_stackbase in struct proc so this is covered by the memcpy
above, in a separate commit so we can pull this one up without any
change to the layout of struct proc.
PR kern/60653: posix_spawn(3) causes incorrect stack base information
execve(2): Set p_stackbase in execve_runproc, not execve_loadvm.
execve_loadvm must not have side effects on the running process for
two reasons:
1. If execve(2) fails, it has to be able to back out and return to
the calling process. For example, the shell will execute the
first of a series of candidate paths that works when it searches
$PATH, and if one fails, it has to be able to move on to try the
next.
2. The caller may be the _parent_ process -- this is the case when
we're in posix_spawn.
Instead, it must be set in execve_runproc, after we're committed to
the exec and can't back out -- and we're definitely operating on the
process that is executing a new image, not on its parent!
p_stackbase and its assignment in exec_setup_stack, a subroutine of
[18 lines not shown]
t_signal_and_sp: Link against libpthread unconditionally now.
Required by new test cases added for:
PR kern/60653: posix_spawn(3) causes incorrect stack base information
Test various methods of getting the process's stack base and size.
And test the effect of fork, vfork, failed execve, and posix_spawn on
them.
PR kern/60653: posix_spawn(3) causes incorrect stack base information
exec: Free struct exec_package::ep_emul_arg in more error paths.
We should really formalize the destruction path for these temporary
exec data structures; these error branches are all tangled messes of
spaghetti.
PR kern/60657: panic: kernel diagnostic assertion "epp->ep_emul_arg
== NULL" failed: file
"/home/riastradh/netbsd/current/src/sys/kern/kern_exec.c", line 535
Test case forthcoming (it would panic the testbed) as part of
PR kern/60653: posix_spawn(3) causes incorrect stack base information
which is how I stumbled upon this.
fdt_pinctrl: don't skip pinctrl entries
Per the DT-bindings, pinctrl-n is a list of phandles, so a phandle every four bytes. If pinctrl-cells is more than one, the current code skips some phandles in the list since it advances by 4*pinctrl-cells bytes per entry.
This part of the code should not need to touch pinctrl-cells at all. pinctrl-cells is only relevant for the pinmux entries *inside* the pin controller, not for pin controller consumers.
This fixes the spi pinctrls on the am18xx.
pinctrl_simple: support bit-per-mux
pinctrl-single,bit-per-mux is an alternate mode some devicetrees use.
This enables using pinctrl_simple on the TI am18xx.
Pull up following revision(s) (requested by andvar in ticket #445):
sys/arch/x86/x86/identcpu.c: revision 1.143
Temporarily disable SMAP for CPUVENDOR_IDT vendor CPUs (if available).
SMAP feature causes a supervisor page fault during boot on KX-7000 CPUs.
port-amd64/60641
