| Age | Commit message (Collapse) | Author |
|---|
|
OK tb@ claudio@
|
|
|
|
|
|
Instead of burning one letter for each new file format (sidrops is known
to crank out new things faster than a normal person can read), use -x to
opt into parsing and processing file formats that aren't yet considered
stable. This is currently only the Signed Prefix List. While a repetition
of the ASPA debacle, this code hasn't yet seen enough stress testing to be
enabled by default.
ok claudio job
|
|
ok claudio job (as part of a larger diff)
|
|
These were incorrectly added to asn1.h. OPENSSL_gmtime is in crypto.h
and OPENSSL_timegm is already in posix_time.h
|
|
Likely doesn't work.
|
|
|
|
|
|
|
|
OK deraadt@
|
|
ok bluhm@
|
|
Do not call exit 0 in parent and child process. This skiped the
testing in multiple subtests. Use meaningful variable names to
figure out what is going wrong after the tests have been enabled.
Fix the test logic. Add missing break in switch statement, so that
success is reported.
|
|
|
|
|
|
X509_ALGOR_set0_evp_md()
|
|
|
|
|
|
|
|
The nanosleep regression test used gettimeofday(2). Switch it to
a monotonic clock to avoid accidential fails from a call to
settimeofday(2) somewhere in the system.
from Christian Ludwig
|
|
|
|
high limits, beyond what we actually expect. We already restored
the IDTR from scratch, but the restore of the GDTR (limit) was
removed in r1.10. Put that back in a simpler way, simplify the
IDTR restore and delete the save/restore of the LDTR because that
one really is handled as we want by vmm.
ok dv@ mlarkin@
|
|
It breaks NFS.
ok claudio@
|
|
This silences warnings about a full Rx ring which the Linux driver is
likewise suppressing. They appeared because I used the wrong error code,
ENOBUF vs. ENOSPC.
|
|
This leak is of little consequence in station mode, but would be
problematic in hostap mode.
|
|
|
|
From Gustavo Sousa
in drm-intel-next
|
|
rdomain as the vnetid.
|
|
For the interval and profile providers, schedule the first clock
interrupt to occur dp_nsecs nanoseconds after the start of recording.
This makes the interval between the start of recording and the first
event consistent across runs.
With input from claudio@. Simplified by claudio@.
Thread: https://marc.info/?l=openbsd-tech&m=170879058205043&w=2
ok mpi@ claudio@
|
|
|
|
ok jsing
|
|
OK claudio@
|
|
From Christian Ludwig, ok claudio@
|
|
ok claudio@ deraadt@
|
|
ok jsing
|
|
Before changing the routing code, get IPv4 and IPv6 input, forward,
and output in a similar shape. Remove inconsistencies.
OK claudio@
|
|
cases together since they are kind of the same.
OK tb@
|
|
|
|
|
|
ok kettenis@
|
|
things are going, it will take another decade before it does. But OpenBSD
has it enabled *by default* already.
Drop the #ifdef __linux__. This should hurt other OSes when they finally
catch up with us.
ok robert@, tb@
|
|
Avoid conflicts where alignment is specified later in the underlying
assembly.
ok tb@
|
|
|
|
|
|
Fill and check the cache and call rtalloc_mpath() together. Then
the caller of route_mpath() does not have to care about the uint32_t
*src pointer and just pass struct in_addr. All the conversions are
done inside the functions. ro->ro_rt is either valid or NULL. Note
that some places have a stricter rtisvalid() now compared to the
previous NULL check.
OK claudio@
|
|
Setup inits the context and adds the seed. The buf function simply adds
a block from the file to the hash. The final function calls MD4_Final()
to close the context and generate the hash.
This will help to remove the mmap in the sender and should result in a
more atomic view of the file since hash_file() is now called together
with the other hash_functions.
OK deraadt@ tb@
|
|
down the device tree node. This is necessary form boards that use ytphy(4)
such as the OrangePi Zero 3. Note that this means the PHY mode has to be
correctly specified in the device tree. This hasn't always been the case
and it is still wrong in some of the device trees provided by the U-Boot
version in packages that we use for 32-bit Allwinner SoCs. However those
boards typically use a Realtek RTL8211E PHY (rev. 5) and rgephy(4) does
not pay attention to the flags yet. So this commit shouldn't break any
boards that aren't already broken. I'm working on an U-Boot update that
will fix these device trees.
ok jsg@
|
|
|
|
|
|
discovered by the regress tests.
|
