Add new tests traceme_vfork_clone* in ATF t_ptrace_wait*

Added tests:

- traceme_vfork_clone
- traceme_vfork_clone_vm
- traceme_vfork_clone_fs
- traceme_vfork_clone_files
- traceme_vfork_clone_sighand
- traceme_vfork_clone_vfork

All tests pass. Validate that children do not trigger any signals and dead
locks when traced by a vfork(2)ed parent.

(kamil)

Add clone_func() in t_ptrace_wait.h

(kamil)

Validate that clone(2) is handled properly with more ptrace(2) ATF tests

New tests:

- clone[1-8]
- clone_vm[1-8]
- clone_fs[1-8]
- clone_files[1-8]
- clone_sighand[1-8] // disabled temporarily
- clone_vfork[1-8]

Assert that appropriate events are triggered for the combination of:

- PTRACE_FORK
- PTRACE_VFORK
- PTRACE_VFORK_DONE

(kamil)

Fix CVS Id

(kamil)

Add KASAN instrumentation for copyin/copyinstr/copyoutstr. No copyout for
now, because mm.c needs whitelisting.

(maxv)

Fix incorrect CVS Id

(kamil)

Do not test contents of non-existing Xresource file (if X11 sets have
not been installed)

(martin)

Fix CVS Id usage

(kamil)

Fix CVS Id

NFCI

(kamil)

Fix a typo in a comment

NFCI

(kamil)

Fix a typo in a comment

(kamil)

Fix a typo in a comment

(kamil)

Rely on volatile operations in KCOV data types

Extra atomicity isn't needed and makes maintenance burden between CPUs.

Fixes build issue on NetBSD/i386 reported by <msaitoh>

(kamil)

s/ifnets/ifaddrs

(sevan)

the drivers we dlopen need pthread.
I'm not sure about the exact scenario causing failure, but using the
libc pthread stubs isn't sufficient.

fixes one of the glmark2 crashes (at startup with llvmpipe)

(maya)

Revert previous & just use the inets function to handle both address families.
Heads up by <leot>

(sevan)

Fix tyop.

(simonb)

Fix a bug that the duplex of manual media setting may be wrong
when the IFM_GMASK bit other than IFM_[FH]DX is set.

(msaitoh)

KNF. No functional change.

(msaitoh)

Simplify. No functional change.

(msaitoh)

Fix a bug that the duplex of manual media setting may be wrong
when the IFM_GMASK bit other than IFM_[FH]DX is set.

(msaitoh)

Fix a bug that the duplex of manual media setting may be wrong
when the IFM_GMASK bit other than IFM_[FH]DX is set. Same as a part of
FreeBSD r217413.

(msaitoh)

Fix "build.sh syspkgs" error when creating base-util-root package

(uki)

Avoid marking up semicolons.

(wiz)

regen.

(mrg)

fix a couple of errors in the previous.

(mrg)

add a bunch of PCI devices on my systems, and a bunch of similar
ones found in the same sources online (mostly, Intel, AMD, Nvidia
and ASMedia web sites.)  this includes:

- bunch of xeon e5 v3 devices
- bunch of radeon chipsets
- bunch of nvidia chipsets
- bunch of marvell chipsets
- bunch of asmedia chipsets

be more consistent with device naming within some groups.

(mrg)

Fix yet another fiber mediachange fix. Not tested.
- Don't clear bits other than IFM_[FH]DX.
- Always reset PCS when any IFM_[FH]DX bit is changed.

(msaitoh)

Restore sys/ioccom.h.

(msaitoh)

Remove unused macro definitions. OK'd by pgoyette.

(msaitoh)

Generate SREC kernels that YAMON can load.

(simonb)

Remove inclusion of compat/sys/socket.h. It's not required anymore.

(msaitoh)

Be consistent with file^I and include^I.

(simonb)

Force all devices to IPL_VM.  For some reason serial interrupts at
SPL_SERIAL (SPL_HIGH) wedge.  Gets sbmips to ~multiuser (usually with
a bunch of segfaults).

Possibly a gross hack, but not sure the current code ever worked...

(simonb)

be sure to keep cc1_cpu the CC1*_SPEC.

fixes x86 -mtune=native without killing -cxx-isystem.

(mrg)

Revert RockPro64 dts changes made for rk3399_pcie.  This will need to
be re-done differently so as to avoid contention between dts upstream
and our driver.

(jakllsch)

typo

(sevan)

Use a separate variable for IPv6.
Found with npfctl validate.

(sevan)

Switch out deprecated keywords.
Found with npfctl validate.

(sevan)

Use the equivalent FUSE_VERSION. Probably a more adequately named macro for this

(maya)

provide fuse_version

(maya)

Extend LLVM link.mk to handle librt. Use it in Gallium.

(joerg)

revert previous

(maya)

Print bootargs from the environment

Pass the enironment boot args if none are provided by the boot command

(skrll)

Fixup EFIBOT_DEBUG output for non-_LP64 case

(skrll)

Add the NVMM_CTL ioctl, always privileged regardless of the permissions of
/dev/nvmm. We'll use it to provide a way for an admin to control the
registered VMs in the kernel.

Add an associated wrapper in libnvmm.

(maxv)

Try to avoid showing externally visible timing or memory access
differences regardless of whether the derived pwd-value is smaller than
the group prime.

This is related to CVE-2019-9494.

(christos)

This is an initial step towards making the FFC case use strictly
constant time operations similarly to the ECC case.
sae_test_pwd_seed_ffc() does not yet have constant time behavior,
though.

(christos)

These groups have significant probability of coming up with pwd-value
that is equal or greater than the prime and as such, need for going
through the PWE derivation loop multiple times. This can result in
sufficient timing different to allow an external observer to determine
how many rounds are needed and that can leak information about the used
password.

Force at least 40 loop rounds for these MODP groups similarly to the ECC
group design to mask timing. This behavior is not described in IEEE Std
802.11-2016 for SAE, but it does not result in different values (i.e.,
only different timing), so such implementation specific countermeasures
can be done without breaking interoperability with other implementation.

Note: These MODP groups 22, 23, and 24 are not considered sufficiently
strong to be used with SAE (or more or less anything else). As such,
they should never be enabled in runtime configuration for any production
use cases. These changes to introduce additional protection to mask
timing is only for completeness of implementation and not an indication
that these groups should be used.

This is related to CVE-2019-9494.

(christos)

Make the non-failure path in the function proceed without branches based
on r_odd and in constant time to minimize risk of observable differences
in timing or cache use. (CVE-2019-9494)

(christos)

The QR test result can provide information about the password to an
attacker, so try to minimize differences in how the
sae_test_pwd_seed_ecc() result is used. (CVE-2019-9494)

Use heap memory for the dummy password to allow the same password length
to be used even with long passwords.

Use constant time selection functions to track the real vs. dummy
variables so that the exact same operations can be performed for both QR
test results.

(christos)

This algorithm could leak information to external observers in form of
timing differences or memory access patterns (cache use). While the
previous implementation had protection against the most visible timing
differences (looping 40 rounds and masking the legendre operation), it
did not protect against memory access patterns between the two possible
code paths in the masking operations. That might be sufficient to allow
an unprivileged process running on the same device to be able to
determine which path is being executed through a cache attack and based
on that, determine information about the used password.

Convert the PWE finding loop to use constant time functions and
identical memory access path without different branches for the QR/QNR
cases to minimize possible side-channel information similarly to the
changes done for SAE authentication. (CVE-2019-9495)

(christos)

Get rid of the branches that depend on the result of the Legendre
operation. This is needed to avoid leaking information about different
temporary results in blinding mechanisms.

This is related to CVE-2019-9494 and CVE-2019-9495.

(christos)

These functions can be used to help implement constant time operations
for various cryptographic operations that must minimize externally
observable differences in processing (both in timing and also in
internal cache use, etc.).

This is related to CVE-2019-9494 and CVE-2019-9495.

(christos)

This helps in reducing measurable timing differences in operations
involving private information. BoringSSL has removed BN_FLG_CONSTTIME
and expects specific constant time functions to be called instead, so a
bit different approach is needed depending on which library is used.

The main operation that needs protection against side channel attacks is
BN_mod_exp() that depends on private keys (the public key validation
step in crypto_dh_derive_secret() is an exception that can use the
faster version since it does not depend on private keys).

crypto_bignum_div() is currently used only in SAE FFC case with not
safe-prime groups and only with values that do not depend on private
keys, so it is not critical to protect it.

crypto_bignum_inverse() is currently used only in SAE FFC PWE
derivation. The additional protection here is targeting only OpenSSL.
BoringSSL may need conversion to using BN_mod_inverse_blinded().

This is related to CVE-2019-9494 and CVE-2019-9495.

(christos)

Explicitly verify that own and peer commit scalar/element are available
when trying to check SAE confirm message. It could have been possible to
hit a NULL pointer dereference if the peer element could not have been
parsed. (CVE-2019-9496)

(christos)

This adds an explicit check for 0 < x,y < prime based on RFC 5931,
2.8.5.2.2 requirement. The earlier checks might have covered this
implicitly, but it is safer to avoid any dependency on implicit checks
and specific crypto library behavior. (CVE-2019-9498 and CVE-2019-9499)

Furthermore, this moves the EAP-pwd element and scalar parsing and
validation steps into shared helper functions so that there is no need
to maintain two separate copies of this common functionality between the
server and peer implementations.

(christos)

When processing an EAP-pwd Commit frame, the server's scalar and element
(elliptic curve point) were not validated. This allowed an adversary to
bypass authentication, and act as a rogue Access Point (AP) if the
crypto implementation did not verify the validity of the EC point.

Fix this vulnerability by assuring the received scalar lies within the
valid range, and by checking that the received element is not the point
at infinity and lies on the elliptic curve being used. (CVE-2019-9499)

The vulnerability is only exploitable if OpenSSL version 1.0.2 or lower
is used, or if LibreSSL or wolfssl is used. Newer versions of OpenSSL
(and also BoringSSL) implicitly validate the elliptic curve point in
EC_POINT_set_affine_coordinates_GFp(), preventing the attack.

(christos)

When processing an EAP-pwd Commit frame, verify that the peer's scalar
and elliptic curve element differ from the one sent by the server. This
prevents reflection attacks where the adversary reflects the scalar and
element sent by the server. (CVE-2019-9497)

The vulnerability allows an adversary to complete the EAP-pwd handshake
as any user. However, the adversary does not learn the negotiated
session key, meaning the subsequent 4-way handshake would fail. As a
result, this cannot be abused to bypass authentication unless EAP-pwd is
used in non-WLAN cases without any following key exchange that would
require the attacker to learn the MSK.

(christos)

CVE-2019-9498 (EAP-pwd server missing commit validation for scalar/element)
When processing an EAP-pwd Commit frame, the peer's scalar and element
(elliptic curve point) were not validated. This allowed an adversary to
bypass authentication, and impersonate any user if the crypto
implementation did not verify the validity of the EC point.

Fix this vulnerability by assuring the received scalar lies within the
valid range, and by checking that the received element is not the point
at infinity and lies on the elliptic curve being used. (CVE-2019-9498)

The vulnerability is only exploitable if OpenSSL version 1.0.2 or lower
is used, or if LibreSSL or wolfssl is used. Newer versions of OpenSSL
(and also BoringSSL) implicitly validate the elliptic curve point in
EC_POINT_set_affine_coordinates_GFp(), preventing the attack.

(christos)

Remove lingering references to NETBSD_CC1_AND_CC1PLUS_SPEC.
Not actually tested.

(maya)

remove bogus specs redefinition.
fixes the use of -march=native

(maya)

add types for windows and linux partitions.

(mlelstv)

ELRITE is a router .... enable gif(4) by default.

(roy)

adjust miniroot scripts to deal with the time prefix in dmesg

(christos)

Add LLD & LLDD

(sevan)

npf_boot rc script loads npf.boot.conf to address that issue.

(sevan)

Bump date for previous.

(wiz)

Remove mention of SPLASHSCREEN_PROGRESS option.

It was (mostly) removed from the codebase in 2011.

(tpaul)

Replace some "panic()" calls with simple "printf() ; return error"

There's no good reason for these build-time parameters to be allowed to
panic the kernel when it is easy to simply disable the module code and
fail gracefully.

While we're at it, similarly replace panic() when malloc fails to also
fail gracefully.

(pgoyette)

KNF. No functional change.

(msaitoh)

Fix a bug that OSIOCSIFMEDIA can't treat. Add missing inclusion of
compat/sys/sockio.h.

(msaitoh)

PR bin/54112

Fix handling of "$@" (that is, double quoted dollar at), when it
appears in a string which will be subject to field splitting.

Eg:
${0+"$@" }

More common usages, like the simple "$@" or ${0+"$@"} end up
being entirely quoted, so no field splitting happens, and the
problem was avoided.

See the PR for more details.

This ends up making a bunch of old hack code (and some that was
relatively new) vanish - for now it is just #if 0'd or commented out.
Cleanups of that stuff will happen later.

That some of the worst $@ hacks are now gone does not mean that processing
of "$@" does not retain a very special place in every hackers heart.
RIP extreme ugliness - long live the merely ordinary ugly.

Added a new bin/sh ATF test case to verify that all this remains fixed.

(kre)

Ticket #1229

(martin)

Pull up following revision(s) (requested by pgoyette in ticket #1229):

sys/kern/sysv_ipc.c: revision 1.38
sys/conf/files: revision 1.1233
sys/conf/param.c: revision 1.68

defparam all of the config variables associated with SYSV IPC stuff.

The variables were removed from sys/conf/param.c and moved into the
SYSV IPC code, but config options were never propagated via any opt_*
file.

This should fix an issue reported on netbsd-users list from Dima Veselov.
Note that this does not address other parameters included in that report,
including CHILD_MAX and NOFILE; this commit only affects items related to
the SYSV IPC code.  Also note that this does not affect non-built-in
sysv_ipc modules, for which you need to update the Makefile to use any
non-standard config values - just like any other non-built-in modules
which have config params.

XXX Pull-up to -8 and -8-0
XXX Note that there are a couple of panic() calls in msginit() which
XXX really should be changed to simple printf() and then result in
XXX msginit failure.  Unfortunately msginit() currently doesn't return
XXX a value so we cannot indicate failure to the caller.  I will fix
XXX this is a future commit.

(martin)

some items are already done. update and sync with reality.

(ryo)

add missing userret() at the end of md_child_return().
this change make some ATF to pass.

(ryo)

Fix quoting (quotes really do not nest...) and remove a bunch of it
that is harmless, but also pointless (in sh, quotes do not make strings,
everything is a string, rather they hide characters which would have
some other meaning unquoted (like spaces) - quotes are not needed around
strings like "descr" so remove them...

Be more consistent with line wrap style, try to avoid wrapping in the
middle of a (sh) word where possible.  Avoid \ use when it is not needed.

Un-KNF (C style) - sh has no declarations, there is no need to leave
blank lines at the head of a function to mark the end of the declarations.

This should be a NFC - but the quoting really was broken before, just
was probably harmless breakage.

(kre)

KNF, 80 column police, a few other tidy ups (use if (ret == 0) rather
than if (!ret) when ret is not a boolean, and test fopen result against
NULL, for example).

NFCI.

(kre)

PR bin/53999 from rudolf (eq.cz)

Fix cgdconfig to report verification failures with gpt and mbr
verification methods (and not treat them as silent hard errors).
This also causes the cgd to be unconfigured when one of those
verification methods fails.

Add ATF tests to check that bad verification is reported, and
does not leave the cgd configured.

Patches from the PR applied.

(kre)

Whitespace change. No functional change.

(msaitoh)

Fix ifdata"o2n"() macro. This is not a real bug because this macro is not used
from anywhere. Both of SIOCGIFDATA and SIOCZIFDATA use "n2o" because
ZIFDATA is almost the same as GIFDATA except zeroing after read.

(msaitoh)

Make the usermode kernel compile again.

(thorpej)

Avoid a maybe-uninitialized warning by checking for an error return
that might indicate that 'len' was not initialized.

(thorpej)

Add missing semicolon.

(msaitoh)

Include CARP support by default

(sevan)

typo, pasto

(sevan)

Include npf_boot rc.d scripts which loads an interim config early in boot.
By default /etc/default/npf.boot.conf which can be overriden by /etc/npf.boot.conf.

(sevan)

typo, you don't need to specify a prefix & mask

(sevan)

Add a commented out entry for CARP

(sevan)

defparam all of the config variables associated with SYSV IPC stuff.
The variables were removed from sys/conf/param.c and moved into the
SYSV IPC code, but config options were never propagated via any opt_*
file.

This should fix an issue reported on netbsd-users list from Dima Veselov.

Note that this does not address other parameters included in that report,
including CHILD_MAX and NOFILE; this commit only affects items related to
the SYSV IPC code.  Also note that this does not affect non-built-in
sysv_ipc modules, for which you need to update the Makefile to use any
non-standard config values - just like any other non-built-in modules
which have config params.

XXX Pull-up to -8 and -8-0

XXX Note that there are a couple of panic() calls in msginit() which
XXX really should be changed to simple printf() and then result in
XXX msginit failure.  Unfortunately msginit() currently doesn't return
XXX a value so we cannot indicate failure to the caller.  I will fix
XXX this is a future commit.

(pgoyette)

bump date

(sevan)

ParseDoDependency: free paths rather than assert

PR: 52737
Reviewed by: christos

(sjg)

Drop Pp before Bl

(sevan)

New sentence, new line

(sevan)

Use MIN_PAGE_SHIFT if PAGE_SHIFT is not available instead of MAX_PAGE_SHIFT.

(christos)

Need pthread for all the mtx_lock.

(maya)

Expand all @@ things in pkgconfig file.
claim TLS.
pick up the list of private libs from pkgsrc mesalib
GL_LIB got renamed to GL_PKGCONF_LIB.

(maya)

Add workaround for non-zero initialized initial-exec TLS variables.
NetBSD doesn't support these with dlopen.

Ref:
https://bugs.freedesktop.org/show_bug.cgi?id=35268
https://mail-index.netbsd.org/pkgsrc-users/2015/09/11/msg022180.html
http://gnats.netbsd.org/50277

Fixes dlopen of libGL reported by prlw1 on current users.
From tnn, via pkgsrc/graphics/MesaLib*.

(maya)

Add instructions on how to determine the scheduler in use.

(sevan)

KNF. No functional change.

(msaitoh)

- Use uint16_t more for MII registers.
- Whitespace.

(msaitoh)

mention that -B is used to set the timeout for mbr_bootsel

(tnn)

EXYNOS5422_DISABLE_CA7_CLUSTER isn't required anymore

(skrll)

Fix a bug that media setting for fiber didn't work correctly. Not tested.
The BUGS section in gem(4) manpage says:

> BUGS
(snip)
>      On the SX fibre variants of the hardware, the link will stay down if
>      there is a duplex mismatch.  Also, packet transmission may fail when in
>      half-duplex mode.

Is the bug related to this fix?

(msaitoh)

Make it compilable with IX_DEBUG.

(msaitoh)

KNF. No functional change.

(msaitoh)

Make it compilable with EF_DEBUG.

(msaitoh)

Fix softc size in CFATTACH_DECL_NEW

(skrll)

- Use the correct function name for the panic message.
- KNF.

(msaitoh)

Make it compilable with AI_DEBUG.

(msaitoh)

KNF. No functional change.

(msaitoh)

Fix a bug that the supported media can't passed correctly. Not tested.

(msaitoh)

KNF. No functional change.

(msaitoh)

Fix previous.  P is the final (relocated) address not just the offset.

(uwe)

Support R_SH_REL32 (encountered in .eh_frame).

(uwe)

- free empty page tables pages if reach a certain usage.
- need to lock at removing an old pg (_pmap_remove_pv) in _pmap_enter()

(ryo)

Offer a potential workaround to the caveat.

(sevan)

The typecnt refers the to ttis array and the timecnt refers to the type array.
The types array can have 0 elements (i.e. timecnt == 0), but the ttis array
needs to have one element (typecnt >= 1). Need to revisit and take into
account the types array.

(christos)

Reset so_cred to NULL after freeing it, because close() may leave the PCB
in pcblist, and we don't want a future lookup (via eg netstat) to read
freed data.

Detected by KASAN, reported by Alexander Nasonov.

(maxv)

Switch to MODULE_CLASS_MISC, from pgoyette@.

(maxv)

Don't forget to call (*machine_destroy) when killing VMs.

(maxv)

Use the fd_clone approach, to avoid losing references to the registered
VMs during fork(). We attach an nvmm_owner struct to the fd, reference it
in each VM, and identify the process' VMs by just comparing the pointer.

(maxv)

Fix minor bugs.
- sc_lock should use an adaptive lock.
- yds_round_blocksize: fix typo.
- yds_trigger_output: fix typo. SlotControlData is pbankoff.
  ptbloff points to ControlData.
- yds_halt_input: fix wrong and extra sc_rec.intr.

(isaki)

White space -> TAB, fix indent, and add RCS Id.
No functional changes intended.

(isaki)

Add the R_ALPHA_BRSGP relocation type.

(thorpej)

Remove superfluous comma. Try improving a sentence. Remove duplicate sentence.

(wiz)

Update comment to match existing function name.

(maya)

Update to reference the newer (committed long ago) API.

With comments from Rocky Hotas on netbsd-docs, thanks.

(maya)

Improve kernel module validation.  First, set a limit on how much of the
module name field to check when validation name's length.  Second, check
the module's mi_class to ensure it is valid.

Update the commenet in sys/module.h to indicate that the module classes
are now being validated.

(pgoyette)

Add a MODULE_CLASS_MAX value to the enum

(pgoyette)

Split the description for EINVAL into two pieces, one for each operation
that can generate the error.

(pgoyette)

Improve wording.

(wiz)

Fix a comment.

(skrll)

Make it compilable with BNX_DEBUG.

(msaitoh)

Add some additional CPU and system types.

(thorpej)

Make explicit note that MODULE_CLASS_ANY should note be used as the
class of a MODULE().  MODULE_CLASS_ANY is intended only to indicate
a "wildcard" match when (auto)loading modules.

(pgoyette)

don't print ???, requested by kre@

(christos)

npf.conf(5): Add more info about ifaddrs().

(rmind)

Switch kcov module class to MODULE_CLASS_MISC

MODULE_CLASS_ANY is not intended to be used by modules.

Noted by <pgoyette>

(kamil)

bump

(christos)

Remove unused definitions.

(These appear to have existed in old-drm)

(maya)

don't return void

(christos)

- we re-define u{int,short,char} in types.h
- handle lint

(christos)

prevent re-definitions from drm.h

(christos)

Add -r so that we get the location of redefinitions

(christos)

make trap 0x70 a TRAP() not UTRAP().  we should be able to handle
fast ECC error as a normal trap, and i saw this once a few years
ago but it never repeated so i haven't been able to test this.

(mrg)

If Command List Override is not supported by the controller, the FIS setting
the WDC_RST bit will fail if the drive already has BSY or DRQ set.
In this case, reset the channel and retry the drive reset.
With this, the drive reset will succeed after a atactl sleep command on
a controller without the CLO feature.

(bouyer)

Fix stack protector build.

(christos)

Exclude references to _ucas_{32,64}_mp() for _RUMPKERNEL.

(thorpej)

Add a test to make sure an overflowing-into-kernel-space  fetch/store near
vm_max_address fails with EFAULT.

(thorpej)

Call com_init_regs() in eumbcnattach() to set up com port register mapping.
Fixes broken console output after changes to remove COM_REGMAP.

(jdc)

VAXinate (No IEEE math)

(christos)

only need to initialize the first type.

(christos)

Don't try to print NULL if we can't get a timezone name. First we try dst,
then we try the non-dst name and finally we just print ??? if that did not
work. This is not needed to handle the "TZ= date" case which was crashing
before because the default timezone was not consistently initialized, but
should handle any timezone now.

(christos)

Add a paranoid racy lock check in child_return()

In theory a child could be detached for some reason or another during
the time window between checking for PSL_TRACED and acquiring proc_lock.

Acquire the proc_lock mutex and recheck for PSL_TRACED before emitting
SIGTRAP. sigswitch() must acquite it internally anyway so this does not
have a negative impact and adds an extra sanity check.

For !PSL_TRACED case there is no impact.

(kamil)

Initialize the default timezone a bit more so that tzgetname(3) works.

(christos)

Invert the filtering priority: now the kernel-managed cpuid leaves are
overwritable by the virtualizer. This is useful to virtualizers that want
to 100% control every leaf.

(maxv)

Claim ifunc support on a number of architectures.
(Architecture list taken from src/tests/libexec/ld.elf_so/t_ifunc.c)

This is needed for attribute target_clones to work.

Non-functional until a mknative run. Tested by doing a regular GCC build.

(maya)

don't append to nbsd_tm_file. This is the sole definition so fine to do.
Only done to reduce diff to upstream.

(maya)

...and now I really have the list of arch versions that require the armv2
style of ufetch_16/ustore_16.  And since it's so many, just stop naming it
for the arch version, and name it for the instruction capability.

(thorpej)

Sync, and fix grammar.

(maxv)

Reduce diff to upstream  (in config.gcc):
Make the NETBSD_ENABLE_PTHREADS unconditional (we don't use the else case)

(maya)

Make the post-netbsd 2.0 case the only case. NFC.

(Reducing diff to upstream)

(maya)

Don't allow unloading when there are still VMs registered, and don't allow
auto-unloading at all. Not a big problem actually, because since I changed
the module class it's not auto-loadable anymore.

(maxv)

Explicitly include bold8x16 and bold16x32 fonts

(jmcneill)

Add "bold16x32", a pixel doubled version of the "bold8x16" font.

(jmcneill)

Ticket #1228

(martin)

Pull up following revision(s) (requested by bouyer in ticket #1228):

sys/dev/pci/if_bge.c: revision 1.328

Fix ASIC check, BGE_ASICREV(sc->bge_chipid) is not a chipid.

Fixes bogus input error reporting in stat. This is cosmetic, exept for
routed(8) which thinks that the interface is broken and stops accepting routes
from it.

(martin)

Really implement WDF_DIRTY. patch(1) did something silly here ...

(bouyer)

blkif_x86_{32,64}_* are not identical to blkif_*, internal fields have
different alignements and this change their sizes. Copy them back from
their netbsd-8 definitions.
Fixes PR port-xen/54099

(bouyer)

Adjyst some debug printfs

(bouyer)

Ticket #1227

(martin)

Pull up following revision(s) (requested by rin in ticket #1227):

sys/dev/ic/msm6242b.c: revision 1.4

Remove misplaced semicolon, found by GCC 6.

(martin)

Provide a code argument in kasan_mark(), and give a code to each caller.
Five codes used: GenericRedZone, MallocRedZone, KmemRedZone, PoolRedZone,
and PoolUseAfterFree.

This can greatly help debugging complex memory corruptions.

(maxv)

Fix tiny race in pool+KASAN, that resulted in occasional false positives.

We were uselessly marking already valid areas as valid. When doing that,
our KASAN code emits two calls to kasan_markmem, and there is a very small
window where the area becomes invalid. So, if the area happens to be
already globally referenced, and if another thread happens to read the
buffer via this reference, we get a false positive.

This happens only with pool_caches that have a pc_ctor that creates a
global reference to the buffer, and there is one single pool_cache that
does that: 'file_cache'.

So now, two changes:

- In pool_cache_get_slow(), the pool_get() has already redzoned the
  object, so no need to call pool_redzone_fill().

- In pool_cache_destruct_object1(), don't re-mark the object. If there is
  no ctor pool_put is fine with already-invalid objects, if there is a
  ctor the object was not marked as invalid in the first place; so in
  either case, the re-marking is not needed.

Fixes PR/53674. Although very rare and difficult to reproduce, a local
quarantine patch of mine made the false positives recurrent.

(maxv)

workaround gcc/vax bugs

(maya)

Bump for recent Mesa update.

(rin)