| Age | Commit message (Collapse) | Author |
|---|
|
HW-specific data and CRC trailer as intended, the driver was telling the
net80211 layer frames were longer than they actually are. Math is hard.
ok krw@ kettenis@ mpi@
|
|
|
|
|
|
instruction depend on ci->ci_cpl makes the compiler generate strange code
and might not be enough to stop the compiler moving instructions around.
ok jsing@
|
|
you live (e.g., it expects to be able to get back to the directory it
started from, even when this one wasn't readable in the first place).
Do an extra chdir('/') to try to sidestep the issue.
|
|
|
|
|
|
mask. Also remove redundant imsg_event_add calls. Fixes come from
usr.sbin/ospfd/control.c
ok reyk
|
|
(From Martin Brejcha)
OK from tedu@, miod@ and deraadt@
|
|
protocol checksum offload, where tcpdump might see bad checksums on
valid packets.
ok henning@ jmc@
|
|
logic in the dedicated signal stack case, too.
Also, every time the sigcontext position is recomputed by the above logic,
recheck the DAE addresses from the beginning, in case a formerly avoided
address now risks being overwritten.
|
|
ok miod@
|
|
commit messages that fixes this says:
"it was intentionally left broken as an optimization".
right!
ok martynas@, daniel@
|
|
ok espie
|
|
|
|
|
|
|
|
The underlying code has long been removed, making this a no-op.
If your random subsystem actually requires that you seed it from a file,
then you really should go and buy a new random subsystem that was built
after 1990.
Diff from Brent Cook.
ok deraadt@
|
|
of the intel RDRAND instruction. Consensus was RDRAND should probably
only be used as an additional source of entropy in a mixer.
Guess which library bends over backwards to provide easy access to
RDRAND? Yep. Guess which applications are using this support? Not
even one... but still, this is being placed as a trap for someone.
Send this support straight to the abyss.
ok kettenis
|
|
|
|
system. This function checks for unicast and broadcast addresses, so
there is no need to do two lookups instead of one.
Inputs & ok jca@, ok mikeb@
|
|
|
|
error handling code paths (ex. wrong/unsupported mode).
|
|
remove empty dev_mon_snoop() function
|
|
- \*Gt -> >, as recommended by schwarze
ok guenther
|
|
isn't even exported, there's no (sane) way for someone else to use the
typedef. Eliminate the typedef and just use "struct _pqueue *".
duplicate typedef pointed out by Brent Cook (busterb (at) gmail.com)
ok miod@
|
|
this nasty function.
This gets rid of the nasty tmp variables used to hold temporary strings
and the DECIMAL_SIZE hack. it gets rid of the rather pointless null checks
for buf (since the original code dereferences it before checking). It also
gets rid of the insane possibility this could return -1 when stuff is
using the return values to compute lengths All the failure cases now
return 0 and an empty string like the first error case in the original
code.
ok miod@ tedu@
|
|
ok guenther
|
|
|
|
OK sthen@ miod@
|
|
meaningful variable names with pointer arithmitic, rather than n, i, j
and p with array indexing.
Based on Adam Langley's chromium diffs.
ok miod@
|
|
results in the key block length calculation also being correct. Rename a
number of variables so that their purpose becomes clear and simplify some
of the code.
Inspired by Adam Langley's chromium diffs.
ok miod@
|
|
|
|
since all other characters are mapped through transparently.
ok jsing
|
|
memset(a->data, 0, (unsigned int)a->max);
but the decl is:
size_t max;
size_t could be larger than int, especially in some of the systems OpenSSL
purports to support.
How do _intentionally truncating_ casts like enter into a codebase?
Lack of understanding of C, at a minimum. Generally the objects are
small, but this code is _intentionally unready_ for large objects.
ok miod
|
|
|
|
in this file directly use __attribute__.
ok deraadt@
|
|
ok deraadt@
|
|
fixes to keep building.
|
|
infrastructure.
The following tests have not been imported, for their code lacks a licence:
asn1, rsa, sha256, sha512, wp.
|
|
making sure the sigcontext will not overlap pending DAE accesses.
Fixes sporadic sys/kern/signal/earlysig regress failure.
|
|
|
|
since the calculated value is not actually used in the uninitialised case.
Change the code so that we only do the calculation if we actually need it.
Issue detected by clang and reported by both brad@ and Brent Cook.
|
|
|
|
single variable with a descriptive name, instead of two poorly named
variables.
Largely based on Adam Langley's chromium patches.
ok miod@
|
|
removes the need for zero values to be specified (meaning that we usually
specify two fields instead of 12), makes the field names grepable and
protects from future field reordering/removal.
ok beck@ miod@
|
|
were to be enabled, it had a bug that prevented it from working anyway.
ok deraadt@, kettenis@
|
|
from Brent Cook
|
|
Sure miod@
|
|
|
