awk(1): Another echo(1) example that demonstrates field assignment

(uwe)

awk(1): Use .It Xo Fo trick to format optional arguments correctly

(uwe)

awk(1): Document /dev/stdin &c magic names (NB: unrelated to fd(4))

(uwe)

awk(1): Factor out output redirection for print and printf.

This makes the description way less cluttered and explicitly shows
"| expr" (that was mentioned, but not written out) and ">> file" (that
was not even mentioned at all).  Adapted from the POSIX wording, but
doesn't bring over all the detailed verbiage.

(uwe)

Remove unnecessary multiple inclusion protections.

(tsutsui)

awk(1): A few more formatting tweaks to inlibe code bits and pieces

(uwe)

Remove unnecessary and incorrect mulitple inclusion protection.

(tsutsui)

awk(1): Fix editing accident in one of the previous commits.

(uwe)

awk(1): Drop whitespace between initials

P.J. requires thin space, for other - V and W has enough natural space
near the bottom (the intervening dot prevents kerning).

(uwe)

awk(1): more formatting nits

(uwe)

awk(1): drop POSIX prescriptive "shall" from the otherwise descriptive passage

(uwe)

awk(1): Fix mark up of inline code, the easy cases for now.

(uwe)

awk(1): mark up $<n> properly - '$' is an unary op, not part of the name

(uwe)

awk(1): document programs that only has BEGIN and/or END pattern-actions.

Copied from POSIX, except "getline" is a statement, not a function, so
call it that.

(uwe)

awk(1): document what assigning to $0 and $<n> does

(uwe)

awk(1): mark up var=value properly

(uwe)

awk(1): Fix -width.

"indent" (or misspelings thereof) is not a magic value for -width.

(uwe)

awk(1): g/c extraneous space in an example

(uwe)

awk(1): use official echo example from POSIX

(uwe)

Build dtb files for the Tegra TX2

(martin)

awk.1: revert changes to example 'echo' program

I had removed the exit statement in the strong belief that POSIX had
specified that an AWK program consisting of only a BEGIN block would
implicitly exit after the BEGIN block.  This assumption was wrong.
There are several implementations that implement this special case
though.

https://mail-index.netbsd.org/source-changes-d/2022/07/03/msg013718.html

(rillig)

Be less tautological and more explanatory in a comment.

(skrll)

lint: do not treat message IDs as arithmetic numbers

No functional change.

(rillig)

lint: remove unused code in consistency checker

(rillig)

s/bounaries/boundaries/ in comments.

(andvar)

lint: extend implementation documentation

(rillig)

Use __func__ to print function names.

(tsutsui)

Use proper TAILQ(3) macro as other bus_dma(9) implementation.

No binary change.

(tsutsui)

Misc KNF.  No binary change.

(tsutsui)

Fix inverted logic.  My fault back in 2015..

(tsutsui)

Move the iomem extent stuff managed by bus_space(9) and make them static.

Inspired by MD bus_space(9) implemantation of arc.
Briefly tested on TT030.

(tsutsui)

Make local cdevsw functions static.

XXX: there is no config file that has leo(4) (though it still compiles)

(tsutsui)

lint: include the width of bit-fields in the type name

(rillig)

lint: add debug logging for struct and enum details

(rillig)

libXaw: suppress lint warnings about pointer casts

Typical example:

TextAction.c(373): warning:
    pointer cast from 'pointer to struct _WidgetRec'
    to 'pointer to struct _TextRec' may be troublesome [247]

(rillig)

(skrll)

KNF

(skrll)

Perform a BUS_DMASYNC_POSTREAD on the bge_status_block before reading from
it as required by bus_dma(9).

(skrll)

fix various typos in comments, mainly s/pallete/palette/.

(andvar)

awk.1: remove trailing space in output of 'echo' example program

(rillig)

lint: verify that comment above warning_at matches the message

No binary change.

(rillig)

Fix core dump caused by
ksh -c '(i=10; echo $((++-+++i)))'
reported by Steffen Nurpmeso (not on a NetBSD list or PR).

Seems pointless to fix just one of the bugs in this thing, but this one was
easy enough (and stupid enough).  (The "i=10" part is unimportant, as is the sub-shell).

(kre)

Cosmetic tweak.  No functional change.

(ad)

s/refrences/references/

(andvar)

s/tempurature/temperature/

(andvar)

Use aprint_*(9) for attach messages and misc KNF.

(tsutsui)

Use aprint_normal(9) for attach messages.

(tsutsui)

lint: allow message IDs to be only specified in decimal

The message IDs are communicated in decimal everywhere, there's no point
in passing '-X 0x00000084' instead of the clearer '-X 132'.

(rillig)

lint: prevent undefined behavior when folding '<<' or '>>'

(rillig)

lint: document usage of 'convert'

No functional change.

(rillig)

lint: only convert the right operand of '<<' or '>>' in traditional C

Traditional C says: "Then the right operand is converted to int".

C90 dropped that sentence, probably because it didn't have any effect on
the result or the conditions for undefined behavior.

To stick to the wording of the specification, also convert UINT to INT.

While here, fix the call to 'convert'.  The first argument being 'CVT'
means that the conversion comes from a cast-expression instead of an
implicit conversion.  This prevents warnings for 'uint64_t << uint64_t'.
Keeping this unnecessary conversion in C90 or later would have generated
warnings for the functions at the bottom of msg_132.c.

(rillig)

tests/lint: test bit shift with large integer types

build_bit_shift converts the right-hand operand to INT or UINT, even
though C11 6.5.7 doesn't say anything about narrowing conversions.

Traditional C says that the operators '<<' and '>>' perform the usual
arithmetic conversions.  This has been dropped in C90.

What lint actually does is something completely different.  In the
operators table in ops.def, the operators '<<' and '>>' are not marked
as performing the usual arithmetic conversions (column 'balance').  This
leaves all conversions to 'build_bit_shift', which converts the
right-hand side to INT or UINT.  There is no obvious reason for this
conversion, as the bounds checks need to be performed no matter whether
the type is INT or UINT128.

(rillig)

Misc KNF. No binary change.

(tsutsui)

KNF. Remove brackets around return values.

(skrll)

Use and print consistent CPU/MMU/FPU names.

(tsutsui)

One timeout message (the write one) in bge_miibus_writereg is enough.

(skrll)

Modernise bge_update_all_threshes.  Same code before and after.

(skrll)

Misc cleanup.

- make local variables static
- use __func__ to print function names
- KNF

(tsutsui)

Use queue(3) macro as hp300 etc.  No binary change.

(tsutsui)

Simplification.  Same code before and after.

(skrll)

Use C99 types.  same code before and after.

(skrll)

Sprinkle some BITS(3).  Same code before and after.

(skrll)

Use BUS_ADDR_{LO,HI}32. NFCI.

(skrll)

More const. Remove strange ifp assignments in bge_init.

(skrll)

Use PRIxBIT instead of casts

(skrll)

wm_tick: Add missing splx(s) when not WM_MPSAFE

(skrll)

sort previous

(skrll)

Make this compile again.

(skrll)

Add a missing ';'

(skrll)

drm: Rewrite drm_gem_cma_helper.h from scratch.

The header file was originally part of drm with no licence text,
which I took to mean BSD-licensed like the rest of the Linux drm code
base is by default -- everything in Linux under include/drm and
drivers/gpu/drm not otherwise marked.

In 2017, a tree-wide automated change was applied to Linux which
caused an SPDX GPL header to appear in drm_gem_cma_helper.h.  When I
asked the drm developers about this in drm files, they explained that
it was an automated process and many of the SPDX headers were wrong,
so when excluding GPL files in drm updates, I heeded the actual GPL
vs BSD/MIT licence text and revision history rather than the SPDX
headers.

I excluded drm_gem_cma_helper.c because it was clearly originally GPL
as an exception to the default BSD licence under Linux's
drivers/gpu/drm, and Jared reimplemented the API for ues by some
(NetBSD, BSD-licensed) Arm display drivers.

During an update after that, the header file was lost in the merge
shuffle and I copied it back in without noticing the SPDX header
file.  In retrospect, I see now that it's not clear what the intent
was: the .c file was obviously GPL, and maybe the .h file was
supposed to be too but it wasn't carved out as an exception among the
drm code.

To keep our story simpler, I just drafted a new .h file that provides
a compatible subset of the interface we use, derived from the .c file
Jared wrote, written according to several deterministic rules based
on KNF that yield a non-creative specification of the compatible
interface:

1. $NetBSD$ RCS id
2. standard TNF copyright statement
3. header guard derived from #include file name
4. minimal #includes, grouped and sorted according to KNF
5. forward declaration of structs, sorted lexicographically
6. definitions of structs, members sorted lexicographically by name
7. downcasting macros, written in KNF and sorted lexicographically
8. minimal extern variable declarations, sorted lexicographically
9. minimal, function prototypes, written in KNF and sorted
  lexicographically

`Minimal' means added one by one, according to the errors issued by
the compiler (and in the case of #includes, according to the correct
header file for the missing types or function prototypes being used),
until the compiler is formally satisfied.

Any changes to this will, unless otherwise marked, be covered by the
standard TNF licence now on the file.

(riastradh)

sendto(2), recvfrom(2): Scrub internal struct msghdr on stack.

Otherwise this is kernel stack disclosure via ktrace.

Reported-by: syzbot+1d40303b310063778194@syzkaller.appspotmail.com

(riastradh)

lint: clean up suppression of warnings and errors

Since lint1.h 1.11 from 2001-12-13, lint1 had been a memory hog.  While
it used a bit set for keeping track of the message IDs of the suppressed
messages, it only used the lower 4 bits of each 32-bit word, due to a
missing CHAR_BIT in __NERRBITS.

As a quick hack, the bit set had 1024 entries, much more than the number
of actual messages, which is currently at 350.  This meant 674 bytes of
wasted memory, plus the code size for the bit manipulations.

The only functional change is that the option '-X' now only accepts
actually valid message IDs.  Previously it had accepted all numbers from
0 to 1023.

(rillig)

lint: move error handling code from main1.c to err.c

No functional change.

(rillig)

kern: KNF in kern_time.c: Omit needless return parentheses.

Also nix trailing whitespace while here.

No functional change intended.

(riastradh)

route(4): Use m_copydata, not misaligned mtod struct access.

XXX Maybe this should check rtm_len too like route_output does.

Reported-by: syzbot+d37eaf0a26097572bbbc@syzkaller.appspotmail.com
https://syzkaller.appspot.com/bug?id=3cdfefd8b7938c9606ed68b4191e97fabdbd7b08

(riastradh)

lint: add quotes around operator in message 138, remove message 240

Message 138 doesn't occur in practice, it was the last one that was
missing the quotes around the placeholder.

Message 240 was also missing the quotes, but it was not reachable. There
was also no apparent benefit in warning about 'assignment of different
structures' when the message about 'assignment type mismatch' serves the
same purpose.

(rillig)

tests/lint: add tests for accessing incomplete types

(rillig)

lint: restructure 'convert'

The conditions are now grouped by target type, highlighting that
conversions between integer and floating point types are not checked by
this function, in fact, they are not checked at all.

No functional change.

(rillig)

lint: rename functions for value conversion

No functional change.

(rillig)

Fix At argument and remove superfluous Pp.

(wiz)

Bring shutdown(8) into the 21st century.

I found this juxtaposition in the shutdown man page kind of
interesting:

    time  Time is the time at which shutdown will bring the system down
  and may be the word now or a future time in one of two formats:
  ... [2nd format:] [[[[[cc]yy]mm]dd]hh]mm,  ...
  If the century [cc] is not specified, it defaults to 1900 for
  years [yy] between 69 and 99, ...

In that, all the "[text]" except the one "[[[[["(etc) sequence are my
interjections, The ellipses ("...") represent where I omitted irrelevant
(for here) text.

Interesting yes, bizarre also.  Requiring a future time, and then
defaulting to the (long gone) 20th century (for any random year)
makes no sense at all.    So I fixed it.

In another hundred years or so, anytime from 2100 onwards, but best
left at least a decade into the new century, it will need altering again.
[One could write the code to automate this adjustment, but the man
page would still need updating.]  More significant changes will be
needed as the 101st century approaches (years 10000 and beyond), as
then a 2 digit century will no longer be adequate.  Call me then, and
if I'm able, I'll fix it.

If someone really has a need to schedule a shutdown for sometime
between 1969 and 1999 that can still be done by explicitly giving
the "19" cc value.  It is just no longer ever the default.

Otherwise, now, years 20..90 mean the 21st century (2020..2099)
(the first 2 of those are already unusable, but, IMO, that's OK)
and years 00..19 mean the 22nd century (2100..2119) (except that
00, 2100, is still technically the final year of the 21st century).

This is advance planning for near the end of the 21st century when
someone wants to schedule a shutdown for early in the following
century, and can't be bothered typing the 2 century digits.

(kre)

Uglify code to fix build.

(prlw1)

umidi(4): Clarify loops.  No functional change intended.

(riastradh)

ktrace(9): Zero-initialize padding for ktr_psig records.

Reported-by: syzbot+03fbfa20e6c7a3919a06@syzkaller.appspotmail.com

(riastradh)

upgt(4): Make upgt_free_cmd match upgt_alloc_cmd.

Reported-by: syzbot+365e26863f286c6677b7@syzkaller.appspotmail.com

(riastradh)

uvideo(4): Make alloc logic match free logic.

Reported-by: syzbot+57cdc1be653327f78b6f@syzkaller.appspotmail.com

PR kern/53734

(riastradh)

kern: Omit stale locking comment in proc_crmod_leave.

(riastradh)

uvideo(4): Assert number of units can't overflow.

Not sure if this is true, but at least we'll trap instead of silently
undercount this way.

(riastradh)

kern: Fix comment about precondition of lwp_update_creds.

(riastradh)

posix_spawn(2): Plug leak in proc_alloc error branch.

(riastradh)

fork(2): Plug leaks in proc_alloc error branch.

(riastradh)

sequencer(4): Fix lock leak in ioctl(FIOASYNC).

Reported-by: syzbot+0bfe9054ab0e70ab02e6@syzkaller.appspotmail.com
Reported-by: syzbot+f2c5459483e60dd2c877@syzkaller.appspotmail.com
Reported-by: syzbot+d932ddf0ec7e30784ca8@syzkaller.appspotmail.com

Note: The evidence from
https://syzkaller.appspot.com/bug?id=19e1c8779bb0e020188ca80a586e470b59d7525d
suggests in the stack trace that the syscall was 16, which is chown.
This is not accurate; it happens because the x86 syscall logic sets
rax in the trapframe to the return value (in this case, 16 is EBUSY)
_before_ calling userret which does the lockdebug checks, and ddb
uses the trapframe's rax to show what the syscall number was when
printing its stack trace:

[ 104.0605877] Mutex error: lwp_exit,1084: sleep lock held
[ 104.0605877] lock address : 0xffffd9801269e050 type    :    sleep/adaptive
...
[ 104.5005727] syscall() at netbsd:syscall+0x323 sys/arch/x86/x86/syscall.c:92
[ 104.5115909] --- syscall (number 16) ---

XXX Maybe we should record the syscall number elsewhere so this is
not so confusing -- second time in 24h I've been bitten by this, and
in a different way.

(riastradh)

vfs(9): Avoid arithmetic overflow in lf_advlock.

syzbot+897abbbe59467cbf6e98@syzkaller.appspotmail.com

(riastradh)

KNF some comments

(skrll)

Remove strange (duplicate) assignment.

(skrll)

KNF

(skrll)

doc: Various changes in the past week from various developers

(nia)

Fix rump build failure after sleepq.h:r1.35.

(knakahara)

a driver for Wacom Intuos drawing tablets, from Yorick Hardy
this has been sitting in my tree long enough and works fine with the hardware
I have access to

(macallan)

physio(9): Include error in KASSERTMSG.

May help to track down:
https://syzkaller.appspot.com/bug?id=d57553ea3fc65cb7f11df947154795451b0dd3a8

(riastradh)

route(4): Avoid unaligned access to struct rt_msghdr, take two.

Can't even take the address of the misaligned struct member for
memcpy.  Just copy the header out into a stack variable instead.

Reported-by: syzbot+083d9be5cb3c2e78ed1c@syzkaller.appspotmail.com

(riastradh)

recvmmsg(2): More timespec validation.

Reported-by: syzbot+004ed2f264534bd27312@syzkaller.appspotmail.com
Reported-by: syzbot+6f9014c842c4e78df7bc@syzkaller.appspotmail.com

(riastradh)

sleepq(9): Pass syncobj through to sleepq_block.

Previously the usage pattern was:

sleepq_enter(sq, l, lock);              // locks l
...
sleepq_enqueue(sq, ..., sobj, ...);    // assumes l locked, sets l_syncobj
... (*)
sleepq_block(...); // unlocks l

As long as l remains locked from sleepq_enter to sleepq_block,
l_syncobj is stable, and sleepq_block uses it via ktrcsw to determine
whether the sleep is on a mutex in order to avoid creating ktrace
context-switch records (which involves allocation which is forbidden
in softint context, while taking and even sleeping for a mutex is
allowed).

However, in turnstile_block, the logic at (*) also involves
turnstile_lendpri, which sometimes unlocks and relocks l.  At that
point, another thread can swoop in and sleepq_remove l, which sets
l_syncobj to sched_syncobj.  If that happens, ktrcsw does what is
forbidden -- tries to allocate a ktrace record for the context
switch.

As an optimization, sleepq_block or turnstile_block could stop early
if it detects that l_syncobj doesn't match -- we've already been
requested to wake up at this point so there's no need to mi_switch.
(And then it would be unnecessary to pass the syncobj through
sleepq_block, because l_syncobj would remain stable.)  But I'll leave
that to another change.

Reported-by: syzbot+8b9d7b066c32dbcdc63b@syzkaller.appspotmail.com

(riastradh)

ktrace(9): Fix mutex detection in ktrcsw.

On _entry_ to sleepq_block, l->l_syncobj is set so that ktrcsw
(ktr_csw) has the opportunity to detect whether it's a mutex or
rwlock.  It is critical to avoid ktealloc when we're sleeping on a
mutex because we may be in softint context where ktealloc is
forbidden.

But after mi_switch, on _exit_ from sleepq_block, l->l_syncobj may
have been changed back to &sched_syncobj or something by
sleepq_remove, and so ktrcsw can no longer rely on l->l_syncobj to
determine whether we _were_ sleeping on a mutex or not.

Instead, save the syncobj in sleepq_block and pass it through as an
argument to ktrcsw.

Reported-by: syzbot+414edba9d161b7502658@syzkaller.appspotmail.com
Reported-by: syzbot+4425c97ac717b12495a2@syzkaller.appspotmail.com
Reported-by: syzbot+5812565b926ee8eb5cf3@syzkaller.appspotmail.com
Reported-by: syzbot+8b9d7b066c32dbcdc63b@syzkaller.appspotmail.com
Reported-by: syzbot+909a8e743c967d97f433@syzkaller.appspotmail.com
Reported-by: syzbot+e2a34bb5509bea0bba11@syzkaller.appspotmail.com
Reported-by: syzbot+faaea3aad6c9d0829f76@syzkaller.appspotmail.com

(riastradh)

regen

(macallan)

add some Wacom devices

(macallan)

Use old limit of 32 + 32 bytes to keep combining buffer on stack.
There are no devices on this platform that need more and for larger
values, the driver should be better rewritten.

(mlelstv)

Synchronize SYS_SYSCALL() with other syscall implementations and
call trace_exit() even if trace_enter() returned an error.

PR kern/52166 "syscallemu does not work on sparc (32-bit)"
PR toolchain/56117 "New test failures on amd64 since switch to gcc10"

(hannken)

Don't unregister sensors twice.

(mlelstv)

unregister sensors only when registered.

(mlelstv)

Unmap device registers only when successfully mapped.

(mlelstv)

Bump max transaction size from 32 Bytes to 4kB.

(mlelstv)

Allocate data buffer instead of using the stack.

(mlelstv)

Add CVPM02 BBU support.

(msaitoh)

Fix Swedish keymap of HIL keyboard map.

The problem was reported by Anders Gustafsson and
fix provieded by Miod Vallat on port-hp300@.

(tsutsui)

bind.2: add references to specific protocol families

Referring the reader to "the manual entries in section 4" was too
unspecific to be useful, as that section contains device drivers as
well.

(rillig)

fix references in manual pages to the reference documentation

(rillig)

Note that GCC 10.4 has been released today.

(fcambus)

remove KASSERT() checking for t_oproc at open since assigning this line
discipline to a pty may not have that set. Instead do a runtime check to
ensure that the function exists before calling it, as ttstart() handles it.

Same code in btuart.c, bcsp.c and bth5.c

Reported-by: syzbot+766981eef92a3cd0352a@syzkaller.appspotmail.com

(plunky)

recvmmsg(2): Avoid arithmetic overflow in timeout calculations.

XXX This is not right -- it doesn't actually do anything to time
out...

Reported-by: syzbot+784209d76a94fcc6417b@syzkaller.appspotmail.com

(riastradh)

appleintc: update ci_cpl in pic_set_priority callback

(jmcneill)

Note that src/games/robots now nees a clean rebuild.

(martin)

Sprinkle some const. Same code before and after.

(skrll)

Fix a null-deref

lgtm from mlelstv.

Reported-by: syzbot+ec264ed7faf603906b93@syzkaller.appspotmail.com

(skrll)

Add support for Lichee Pi Zero from Rui-Xiang Guo on port-arm

(skrll)

RAIDframe must be initialized for the RAIDFRAME_FAIL_DISK80 ioctl.

Reported-by: syzbot+048387fcc9a1a3682638@syzkaller.appspotmail.com
Reported-by: syzbot+037d1813186571cb2d38@syzkaller.appspotmail.com

(oster)

kern: Avoid arithmetic overflow in gettimeleft.

Sprinkle assertions in to verify we're monotonically counting the
time left down to zero.

Reported-by: syzbot+5f6a6329d139810dfe3c@syzkaller.appspotmail.com

(riastradh)

tcp(4): Bail early on sendoob if not connected.

XXX Not sure if testing tp->t_template is the right way to discern
this -- I just reached for it because the downstream crash is a panic
on tp->t_template == NULL in tcp_output.

XXX In principle this could try connecting to the address, except
it's not passed down from the logic in uipc_socket.c to tcp_sendoob.

Reported-by: syzbot+a01f4cfec72790855ce2@syzkaller.appspotmail.com

(riastradh)

fstrans(9): KASSERT(a && b) => KASSERT(a); KASSERT(b)

No functional change intended except better diagnostics in case of
crash.

(riastradh)

amd64: Handle __syscall trap frames specially too.

(riastradh)

fix various typos in comments.

(andvar)

s/loobpack/loopback/ in comment.

(andvar)

umidi(4): Fix fencepost in error branch.

Reported-by: syzbot+0bbf3d81c15fd1354759@syzkaller.appspotmail.com

(riastradh)

Enable FANCY mode for debugging purposes:
  - To enable stand still mode (robot is not moving but waiting in place),
    specify a scorefile on the command line called <directory>/stand_still
  - To enable pattern roll mode (robot is changing which move to look first)
    specify a scorefile on the command line called <directory>/pattern_roll

(christos)

downgrade from LOG_ERR to LOG_DEBUG, requested by uwe@

(christos)

KNF a little. No functional change.

(msaitoh)

Add some MegaRAID devices (except Aero series). Not tested.

(msaitoh)

Regen.

(msaitoh)

Add some MegaRAID devices.

(msaitoh)

Add comment. Sort entries. No functional change.

(msaitoh)

Fix editing mishap, should fix the build

(martin)

sendmsg(2): Avoid buffer overrun in ktrace of invalid cmsghdr.

Reported-by: syzbot+efded148140b23425f5c@syzkaller.appspotmail.com

(riastradh)

ktrace(9): Make sure ktrkuser initializes the full ktr_id member.

strlcpy does not; strncpy does.  However, the member must be
NUL-terminated, because kdump uses it, e.g., with printf("%s"), so
expicitly set the last byte to NUL.

Possible fix for a host of sanitizer complaints in syzkaller.

(riastradh)

Remove confusable comment.

The comment was added in tcp_subr.c:r1.124 (2002/03/15).
tcp_drain() is called from softint context only, now.

(knakahara)

setitimer(2): Avoid arithmetic overflow in periodic bookkeeping.

Reported-by: syzbot+93cef6090844ec304cde@syzkaller.appspotmail.com

(riastradh)

opencrypto(9): Fix missing initialization in error branch.

Reported-by: syzbot+8c519140cac567be1ee1@syzkaller.appspotmail.com

(riastradh)

emdtv(4): More attach/detach bugs.

Reported-by: syzbot+9bbfb743349929e2c8c3@syzkaller.appspotmail.com

(riastradh)

setitimer(2): Guard against overflow in arithmetic.

Reported-by: syzbot+6036bc8b6d2b963e3ba6@syzkaller.appspotmail.com

(riastradh)

kern: Use timespecsubok in ts2timo.

Should fix arithmetic overflow.

Reported-by: syzbot+4393a753a7c787abe6e2@syzkaller.appspotmail.com

(riastradh)

kern: New functions timespecaddok, timespecsubok.

Return false if timespecadd or timespecsub with the same arguments
would overflow (possibly in an intermediate calculation), true if OK.

Typical usage:

sys_wotsit(...)
{
...
if (!timespecsubok(x, y))
return EINVAL;
timespecub(x, y, xydelta);
...
}

(riastradh)

amd64: Print effective syscall number for SYS_syscall stack traces.

This time with compile-testing, at least.

(riastradh)

Revert "amd64: Print effective syscall number for SYS_syscall stack traces."

Built the wrong kernel (arm64 is not amd64), oops.  Will redo.

(riastradh)

amd64: Print effective syscall number for SYS_syscall stack traces.

(riastradh)

route(4): Avoid unaligned access to struct rt_msghdr.

Reported-by: syzbot+e0048186a5cc97b1c5a6@syzkaller.appspotmail.com

(riastradh)

umcs(4): Reject invalid interrupt endpoints.

Reported-by: syzbot+cd1e60e112e840e40d0a@syzkaller.appspotmail.com

(riastradh)

s/Ramdom/Random/ in comments.

(andvar)

Use aprint_*(9) for device attach messages.

(tsutsui)

ldpd(8): Fix address of misaligned packed members.

PR kern/56895

(riastradh)

lagg(4): Safely handle misaligned mbufs.

Optimizing for non-strict-alignment architectures -- without falling
afoul of alignment sanitizers or overeager compilers -- is left as an
exercise for the reader.

PR kern/56894

(riastradh)

drm/ttm: Fix potential leak in error branch.

Not likely but let's not leave a rake to trip on.

(riastradh)

arm/aes_neon: Fix formatting of self-test failure message.

Discovered by code inspection.  Remarkably, a combination of errors
made this fail to be a stack buffer overrun.  Verified by booting
with ARMv8.0-AES disabled and with the self-test artificially made to
fail.

(riastradh)

Decorate the HPPA signal trampoline with the appropriate .cfi
directives to allow exception unwind / backtrace across a signal
handler.

(skrll)

Teach the LLVM-derived unwinder about the DWARF pseudo-registers defined
by GCC for HPPA to hold the return address where the signal trampoline
will resume.  XXX Same treatment is needed for HPPA64, but not done as
part of this commit.

Thanks to thorpej for help with this. (ages ago)

(skrll)

Unifdef __ELF__.

(tsutsui)

Consistently use "NetBSD/atari", not "NetBSD/Atari" on tertiary boot.

(tsutsui)

build fix: remove includes of opt_gic.h

(jmcneill)

Add SIGINFO support. Mostly stolen from scan_ffs(8).

(rin)

cpu_reboot: use cpu_halt_others() instead of a (simple) open coded
version of it.

(martin)

gcc is not smart enough to track the equivalence of conditions used
here and warns about an unused value - initialize "code" always.

(martin)

Fix typo

(martin)

PR toolchain/56268

For NetBSD/m68k, program header is erroneously readable from core dump,
although a page containing it is missing. This spoils relocation for
the main executable, and debugging with core dumps becomes impossible,
as described in the PR.

In order to avoid this failure, add consistency check for program header;
for NetBSD, 1st entry of program header refers program header itself. If
this is not the case, we should be reading random garbage from core dump.

Yes, this is a kind of the hackest hack. But, unable to debug with core
dump is critical. Therefore, I commit this workaround temporarily until
the real cause is found and fixed.

Note that this is not a recent regression for GDB nor kernel, as
mentioned in the PR. These from netbsd-8 and -9 fail in the same way
without this hack.

(rin)

Make local devsw functions static.

No visible regression on TT030.

(tsutsui)

Misc KNF and cleanup for readability.

(tsutsui)

PR port-powerpc/56899

Disable 128-bit long double for NetBSD/powerpc.

(rin)

PR port-powerpc/56899

In addition to ``powerpc'', register NetBSD OS ABI also for ``rs6000'',
which is default target for powerpc.

(rin)