| Age | Commit message (Collapse) | Author |
|---|
|
the size of the response we receive for MCC_UPDATE commands (even
though we aren't doing anything with this response yet).
|
|
|
|
|
|
It seems Intel saw a risk of eventually running out of firmware capability
support and API support flags, so yet another such mechanism was added.
If you want to know which variant of a command needs to be used there are
now at least three places to check for related information.
|
|
|
|
|
|
|
|
|
|
and setting them up later on, nowadays it's possible to do both steps in just
one go through tls_config_set_{cert,key}_file(3) so use it and then init TLS.
No functional change.
OK kn@
|
|
hardware support changes include
inteldrm: better support for tiger lake
amdgpu: support for navi12, navi21 "sienna_cichlid", arcturus
amdgpu: support for cezanne "green sardine" ryzen 5000 apu
Thanks to the OpenBSD Foundation for sponsoring this work,
patrick@ for helping adapt rockchip drm, kettenis@ and mpi@
for uvm discussions and various testers.
|
|
This makes it easier to debug if something fails. Add some ${SUDO}
in a way that this tests runs as root or regular user with and
without SUDO set.
|
|
Reported by some grumpy old cheese lover
"looks reasonable" jsg@
ok kettenis@
|
|
while here
|
|
|
|
This was broken when key installation was moved into a task context.
Reported by and confirmed fixed by gnezdo@ and zxystd from OpenIntelWireless
ok gnezdo@
|
|
allowing the actual tests to become less repetitive.
ok bluhm@
|
|
threads. It works well on idle 4 CPU machines, but with load or
fewer cores the distribution of the threads' signal handlers is
worse. Reduce the limit of signals that each thread must receive
from 75 to 50. This should prevent random test fails.
from Christian Ludwig
|
|
suggested by millert@
|
|
|
|
If the user set nmflags == X509_FLAG_COMPAT and X509_NAME_print_ex(3)
failed, the error return value of 0 was misinterpreted as an indicator
of success, causing X509_print_ex(3) to ignore the error, continue
printing, and potentially return successfully even though not all
the content of the certificate was printed.
The X509_NAME_print_ex(3) manual page explains that this function
indicates failure by returning 0 if nmflags == X509_FLAG_COMPAT
and by returning -1 if nmflags != X509_FLAG_COMPAT.
That's definitely atrocious API design (witnessed by the
complexity of the code needed for correct error checking),
but changing the API contract and becoming incompatible
with OpenSSL would make matters even worse.
Note that just checking for <= 0 in all cases would not be correct
either because X509_NAME_print_ex(3) returns 0 to indicate that it
successfully printed zero bytes in some cases, for example when all
three of the following conditions hold:
1. nmflags != X509_FLAG_COMPAT
2. indent == 0 (which X509_print_ex(3) does use in some cases)
3. the name object is NULL or empty
I found the bug by code inspection and proposed an incomplete patch,
then jsing@ proposed this improved version of the patch.
OK jsing@.
|
|
waiting on CPUs that didn't spin up. This will allow us to spin down
CPUs in the future to save power as well.
ok mpi@
|
|
implmentation does not care about ICMPv6, it simply adds static
multicast routes. Multicast routing needs at least two test machines.
Otherwise only send and receive on localhost is tested.
Currently receiving link-local packets via loopback does not work
due to wrong scope id.
Everything is mostly copied from IPv4 regress.
|
|
or used, GitHub issue 2765 from Uwe Kleine-Koenig.
|
|
|
|
- update references version number
- Z_NULL -> NULL; from millert
- terminate function synopses in main body with ";"; from tb
- NULL -> NUL; from tb
- update NAME and SYNOPSIS for added functions
- updated copyright, to match zlib.h
- simplify \-1 -> -1
ok tb
|
|
|
|
|
|
|
|
Empty statements accepted by ksh(1) pointed out by millert@, use of this
non-standard grammar in the installer pointed out by halex@.
ok halex@ millert@
|
|
This avoids a cpu loop for "while do done" and is consistent with
the behavior of AT&T ksh and most other shells. OK jca@ halex@
|
|
ok bluhm@ sthen@ mpi@
|
|
discovery issues with ESP in UDP.
ok bluhm@ sthen@ mpi@
|
|
|
|
By changing files directly on the server and accessing them on the
client or vice versa, specific kernel behavior can be triggered.
Especially using file mmap(2) over NFS is tested.
|
|
|
|
|
|
the code tried to carry state from the quick smr based lookup through
to the actual map update under the mutex, but this led to refcnt
leaks, and logic errors. the simplification is that if the smr based
checks say the map needs updating, we prepare the update and then
forget what we learnt inside the smr critical section and redo them
under the mutex again.
entries in an etherbridge map are either in it or they aren't, so
we don't need to refcnt them. this means the thing that takes an
entry out of the map becomes directly responsible for destroy it,
so they can do the smr call or barrier directly rather than via a
refcnt.
found by hrvoje popovski while testing the stack running in parallel,
and fix tested by him too.
ok sashan@
|
|
removes two diffs between the two.
|
|
removes a handful of diffs between the two.
|
|
|
|
remote to remote copies. with & ok dtucker bz#1164
|
|
Don't flag the EFI SYS partition "DOSACTIVE". Leave that status
to the OpenBSD partition. Reverts part of r1.77.
Problem reported and fix tested by Mihai Popescu. Thanks!
Cluebats from deraadt@ and code bisecting by dv@.
ok kettenis@
|
|
Previously only the provider's display name was used. The text used depends
on how the SIM is configured and not just on the network in use (for example,
an MVNO SIM on another network will often display the MVNO's name rather
than that of the underlying network).
I have a SIM that roams to any network in my country - whichever network
it roams onto, the display name is the same, so you can't tell which
network you're really using. By printing the provider ID (in GSM-land this
is MCC+MNC) it's easy to lookup and check this.
As the provider was printed on the ifconfig line also showing subscriber-id
and ICCID it was already a bit long, and adding the provider-id there is
a bit too much, so move it to the output line showing APN, now looking like
: subscriber-id 2400xxxxxxxxxxx ICC-id 8946203xxxxxxxxxxxxx
: device EM7455 IMEI 01458xxxxxxxxxx firmware SWI9X30C_02.24.0
: APN key provider Tele2 IoT provider-id 23420
|
|
|
|
|
|
|
|
POSIX says `-v' is an option, not an argument; options may take arguments,
as documented in getopt(3).
Programs may take arguments as well, e.g. "prog -v -- arg ...", but these
are usually marked up with `.Cm'.
Change "The arguments are as follows:" to "The options are as follows:" in
`.Fl's DESCRIPTION example to match what most of our base manuals say.
OK schwarze jmc
|
|
neither supports tbl(7) nor eqn(7) input.
If an input file contains such code anyway, tell the user
rather than failing an assert(3)ion.
Fixing a crash reported by Bjarni Ingi Gislason <bjarniig at rhi dot hi dot is>
in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901636 which the
Debian maintainer of mandoc, Michael at Stapelberg dot ch, forwarded to me.
|
|
|
|
|
