Age | Commit message (Collapse) | Author |
|
The polysemous use of "key" was too confusing. Input from markus@.
ok jmc@
|
|
In 2001 login_passwd was made modular so we could use the same
source for passwd and kerberos auth. Now that we no longer have
kerberos integrated we can simplify login_passwd. OK deraadt@
|
|
generate link-greeting smtp-out report event
|
|
|
|
- rename context into localvars, which is more meaningful and less generic
- instantiate the random rumbling at the start of gnode.h with actual
variable names
- explain and group gnode.h variables better
- make some comments terser/more meaningful
okay millert@
|
|
make it obvious
okay millert@
|
|
adjust comments to be more meaningful
reorder predecessors/successors fields in an order that
makes more sense to me.
okay millert@
|
|
fold back BEINGMADE and BUILDING which mean the same thing
GC CYCLE/ENDCYCLE
okay millert@
|
|
- make BufExpand a real function, zap BufOverflow
- sprinkle assert that justify the arithmetic
- use unsigned constants
- fix a bug in the unlikely condition where Buf_printf would exactly
match the buffer boundary and Buf_Retrieve would be called right after
okay millert@
|
|
fix glaring omission
okay schwarze@, jmc@
|
|
"Go for it" kettenis@
|
|
ok claudio@
|
|
it can register smtp-out events
|
|
|
|
to struct dispatcher_remote, this will reduce the smtp-out reporting diff
|
|
reporting
|
|
reporting
|
|
but gather the information from the link-connect reporting event instead.
this removes redundant code and makes it easier to prepare for smtp-out.
|
|
It helps when you commit from the machine you actually tested on.
|
|
implement this feature.
ok blum@ (a while back)
|
|
discarded in lookup process anyways and this goes in the way of smtp-out
work
|
|
non-optional arguments to stop getopt(3) processing.
ok deraadt@
|
|
mmap(), munman(), madvise() and mprotect() are described as planned for
later releases.
A fully functional mmap(2) supporting shared libraries first appeared in
SunOS 4.0 along with msync(2). SunOS 4.1 added madvise(3) and replaced
msync(2) with mctl(2) which was was used to implement msync(3), mlock(3)
and munlock(3).
While some of these functions appear as empty or ifdef'd functions in
4.1cBSD and later it was not until the Mach VM was integrated with Net/2
that most of them were implemented. Though the CSRG releases never
supported shared libraries or madvise(). mlock()/munlock() were not in
Net/2 as they were added by hibler in 1993, but were in 4.4BSD.
madvise(2) was implemented for UVM in NetBSD 1.5 and ported to
OpenBSD 2.7.
For now instead of trying to accurately describe when interfaces
first appeared in other systems correct when they were first available
in CSRG or OpenBSD releases, retaining the text in mmap(2) discussing
SunOS 4.0.
madvise(2) 4.4BSD -> OpenBSD 2.7
mmap2(2) 4.4BSD -> 4.3BSD Net/2
mprotect(2) 4.4BSD -> 4.3BSD Net/2
msync(2) 4.4BSD -> 4.3BSD Net/2
munmap(2) 4.1cBSD -> 4.3BSD Net/2
|
|
|
|
$SSH_AUTH_SOCK, by extending the existing ForwardAgent option to
accepting an explicit path or the name of an environment variable
in addition to yes/no.
Patch by Eric Chiang, manpage by me; ok markus@
|
|
The recent clock_getres(2) changes made it so that clock_getres(2) returns
the granularity of the active timecounter. This is usually much finer
than that of hardclock(9), so we can no longer use clock_getres(2) to
fudge our upper timeout return bound. The test is failing because it
thinks our sem_timedwait(3) call is returning with too much latency.
We can still get the hardclock(9) granularity via the kern.clockrate
sysctl(2), though, so just use that to fudge the upper bound.
While here, we ought to be checking that we return after the requested
absolute timeout, not that we were asleep for a particular interval.
Breakage reported by mpi@.
ok mpi@
|
|
Input from and ok jmc@
|
|
kernel. So we can make the test config stricter. Change the type
of ipcomp bundle flows from use to dontacq.
|
|
ok markus@
|
|
From j@bitminer.ca with input from Andras Farkas, deraadt, joerg@netbsd
"fix however you feel best!" jmc
|
|
compiled with pie or profiling enabled. This was missed when the
independent depend target was removed. Align this target with the
inference rules in bsd.lib.mk. This now creates mcount.d as it should
and fixes 'make clean' which previously left mcount.po.d behind.
ok guenther
|
|
OK mpi@
|
|
OK mpi@
|
|
Rename variables for clarity while here.
OK mpi@
|
|
|
|
than writing a hard-coded bit pattern to this register.
Matches what Intel's Linux driver does, so it should be the right thing to do.
Tested on 8265 by Tracey Emery and myself.
|
|
Matches what iwm(4) has been doing for a long time to ensure that
a good initial Tx rate will be chosen.
Tested by Tracey Emery on AR9281.
|
|
Some peers will eagerly try to negotiate block ack (asking us to reserve
buffer space) before they are done authenticating themselves. No thanks.
Just let them try again later.
ok mpi@
|
|
as well as pulling frames off the Rx block ack reordering queue, when
an incoming frame above the current seqnum window forces us to slide
the window forward, potentially losing frames within the old window.
Leaving the seqnum window out of sync with the queue would cause needlessly
long stalls in traffic until the window moved again for some other reason.
Problem observed on lossy wifi whenever netstat -W indicated an increasing
"input block ack window slides" counter. With this fix, stalled frames can
be observed only for a relatively short amount of time whenever one or more
frames in the current window are lost.
ok mpi@
|
|
OK benno@
|
|
The bind might fail if another daemon is running while the
control socket opening will succeed.
Then we end up with an overwritten control socket, unwind exiting
and no control socket to the already running unwind.
Found the hard way by deraadt
OK deraadt, mestre, kn, pamela
|
|
Even with the latest microcode this is not set on all CPUs with TSX, but
is set on CPUs which don't need MDS mitigations.
MDS mitigations also mitigate TSX Asynchronous Abort (TAA) but aren't
done if the CPU claims to not be affected by MDS (MDS_NO).
According to "Deep Dive: Intel Transactional Synchronization Extensions
(Intel TSX) Asynchronous Abort" CPUs requiring additional mitigations
for this are:
06-8e-0c Whiskey Lake (ULT refresh)
06-55-0{6,7} 2nd Gen Xeon Scalable Processors based on Cascade Lake
06-9e-0d Coffee Lake R
Currently TSX is disabled unconditionally when possible even if TAA_NO
is set.
We don't currently do MDS mitigations on i386. Attempt to disable TSX
regardless to match amd64.
|
|
Even with the latest microcode this is not set on all CPUs with TSX, but
is set on CPUs which don't need MDS mitigations.
MDS mitigations also mitigate TSX Asynchronous Abort (TAA) but aren't
done if the CPU claims to not be affected by MDS (MDS_NO).
According to "Deep Dive: Intel Transactional Synchronization Extensions
(Intel TSX) Asynchronous Abort" CPUs requiring additional mitigations
for this are:
06-8e-0c Whiskey Lake (ULT refresh)
06-55-0{6,7} 2nd Gen Xeon Scalable Processors based on Cascade Lake
06-9e-0d Coffee Lake R
Currently TSX is disabled unconditionally when possible even if TAA_NO
is set.
ok bluhm@ guenther@ deraadt@
tested by bluhm@ on i5-8365U (06-8e-0c).
|
|
printing negative time frames (caused by jumping the system clock back
in time).
OK benno@
|
|
show_rib_detail() and show_rib_brief() functions.
OK benno@
|
|
|
|
Move oSecurityProvider to match the order in the OpCodes enum.
Patch from openbsd@academicsolutions.ch, ok djm@
|
|
openbsd@academicsolutions.ch, ok djm@
|
|
openbsd@academicsolutions.ch, ok djm@
|
|
|