| Commit message (Collapse) | Author | Files | Lines |
|
from Ross L Richardson <openbsd AT rlr DOT id DOT au>, Thanks
ok claudio@
|
|
from Ross L Richardson <openbsd AT rlr DOT id DOT au>, Thanks
ok claudio@
|
|
from Ross L Richardson <openbsd AT rlr DOT id DOT au>, Thanks
ok claudio@
|
|
from Ross L Richardson <openbsd AT rlr DOT id DOT au>, Thanks
ok claudio@
|
|
and call that function not only from both places where copies
existed - when processing text lines and when processing request/macro
lines in conditional block scope - but also when closing a macro
definition request, such that this construction works:
.if n \{.de macroname
macro content
.. \} ignored arguments
.macroname
This fixes a bug reported by John Gardner <gardnerjohng at gmail dot com>.
While here, avoid a confusing decrement of the line scope counter
in roffnode_cleanscope() for conditional blocks that do not have
line scope in the first place (no functional change for this part).
Also improve validation of an internal invariant in roff_cblock()
and polish some comments.
|
|
|
|
it reads better to me. it might be worth considering this for
queue(3) too.
|
|
|
|
|
|
pointed out by tb@, who also provided the diff.
ok tb@ deraadt@
|
|
pointed out by tb@, who also provided the diff.
maybe someone should/could add a Symbols.list here?
ok tb@ deraadt@
|
|
the use of the sample keyword matches similar config in other
products.
NUM can be a number between 2 and 1048576, and is used to divide
0x100000000 into a threshold that is then compared against a randomly
generated number produced by a load of BPF_RND.
having sampling as part of the grammar means you can write things
like "icmp or sample 128". this lets you capture all icmp traffic
and a sample of the rest of the traffic.
ok jmatthew@ kn@ tb@
|
|
clang 10 on armv7 references these when building RAMDISK (-Oz) but not
GENERIC (-O2).
feedback and ok guenther@
|
|
this adds "rnd" and "random" as keywords in the grammar, and handles
them as an arithmetic operator. the decoder recognises the load,
so tcpdump can print it as 'ld #random'. most of the handling is
copied from the "len"/"length" keywoard handling that generates and
decodes a load of the actual wire length of the packet.
ok jmatthew@ tb@ kn@
|
|
this will be used so a bpf filter can make a decision based on a
random number, which in turn will be used so a filter can perform
random sampling of packets rather than capturing all packets. random
sampling means that we don't have to figure out how to make bpf
coordinate multiple concurrent calls to do counter based sampling.
BPF_RND is currently backed with arc4random.
discussed with many including jmatthew@, alex wilson, claudio@,
sthen@, deraadt@, and tb@
ok kn@ tb@ jmatthew@
i call this extended bpf... xBPF.
|
|
|
|
if the user specified a custom extension then the everything would be
in order except the custom ones. bz3198 ok dtucker markus
|
|
default remains to not forward an agent, even when ssh_config enables
it. ok jmc dtucker markus
|
|
comments, which is the style we currently use, and gives too many
boring warnings.
ok djm
|
|
crank due to ABI change.
|
|
ok millert
|
|
it results in the same, but is incorrect.
ok millert
|
|
ok martijn
|
|
removal of the vnode interlock in 2007.
Reported by and original diff from Dominik Schreilechner.
OK jmc@
|
|
Clang 10 warns about the expression sizeof(cdata) / sizeof(uint64_t) as
cdata is an array of uint32_t and it expects that the intent of this is
to compute the number of array elements. Use BCRYPT_WORDS / 2 instead.
Same diff as millert's commit sys/lib/libsa/bcrypt_pbkdf.c -r1.2, which
was ok kettenis. deraadt confirms that this satisfies clang 10.
|
|
|
|
from mortimer
|
|
Copied over from sys/netinet/raw_ip.c:rip_input() where it appeared with
initial support for multiple routing tables.
This enforces separation between multiple raw sockets in different routing
tables, i.e. one must not see packets from the other if the rtable differs.
Observed with ping6(8)'s "-v" showing all ICMPv6 packets on its raw socket
including those produced by another ping6 with "-V1".
florian reported IPv6 route advertisments in one routing table appearing on
raw sockets in other routing tables as well.
OK claudio florian
|
|
In case of AX201 we need to be careful about which devices are matched by
the driver because devices with technical differences share the same PCI
product ID. The driver must additionally match against a table of known
PCI subsystem product IDs to identify an AX201 device correctly.
For consistency, I wrote similar matching code for AX200 devices. This matches
my AX200 device correctly but fails to recognize some other devices which were
previously attached and working.
Turns out the Linux driver seems to use AX200 subsystem product IDs merely
for marketing purposes. It makes the operating system advertise some AX200
devices with distinct trademarked names. There are no technical differences
that concern the driver and there is no exhaustive list of possible AX200
subsystem product IDs. So just match them all.
Problem reported by Bobby Reynolds.
|
|
The write path can return a failure in the AEAD path and there is no reason
not to check a return value.
Spotted by tb@ during another review.
ok tb@
|
|
OK kn@, "fine" deraadt@
|
|
Range violations are now consistently reported as EOPNOTSUPP.
Previously they were mixed with ENOPROTOOPT.
OK kn@
|
|
- Make the DTLS code much more consistent with the ssl3 code.
- Avoid assigning wr->input and wr->length just so they can be used as
arguments to memcpy().
- Remove the arc4random_buf() call for the explicit IV, since tls1_enc()
already does this for us.
ok tb@
|
|
|
|
ssl3_create_record().
ok tb@
|
|
on any platform. Mention this here, as done for AX201 in the iwx(4) page.
|
|
|
|
Matching firmware can be installed with fw_update(1).
Align our device initialization sequence more closely to how Linux does it.
We still use a different MSI-X configuration but register values written
up to that point are now identical.
patrick@ provided help with debugging several issues along way, thanks!
|
|
|
|
|
|
|
|
|
|
from threads other than the one currently having kcov enabled. A thread
with kcov enabled occasionally delegates work to another thread,
collecting coverage from such threads improves the ability of syzkaller
to correlate side effects in the kernel caused by issuing a syscall.
Remote coverage is divided into subsystems. The only supported subsystem
right now collects coverage from scheduled tasks and timeouts on behalf
of a kcov enabled thread. In order to make this work `struct task' and
`struct timeout' must be extended with a new field keeping track of the
process that scheduled the task/timeout. Both aforementioned structures
have therefore increased with the size of a pointer on all
architectures.
The kernel API is documented in a new kcov_remote_register(9) manual.
Remote coverage is also supported by kcov on NetBSD and Linux.
ok mpi@
|
|
|
|
improvements:
- Fix size of the lower case 'ae' character in the 16x32 and 32x64 versions
- Shorten parentheses, square brackets, braces, slash, backslash in the
8x16 version, fixing alignment issues
- Shift vertical line and double vertical line characters one pixel
up in the 8x16 version
|
|
in-progress before we do check for the pipe being halted.
This fixes some kind of race condition for isoc devices during device
close when xp->halted gets set while usbd_start_next() still tries to
dequeue in-progress transfers which will report 'usbd_start_next:
error=13' (USBD_IOERROR).
ok mpi@
|
|
ok mpi@
|
|
it would require a pile of pointless de-const casts in the firmware
construction code.
|
|
atapiscsi is not needed here. (well maybe it changes the behaviour of
the pciide subsystem a tiny bit at attach-time, but we don't have the
downstream cd(4) device to attach, so let's try without)
|
|
Instead of just checking if *namep is NULL, also check if the string
pointed by *namep is empty. This is probably the original intent of
the code.
OK kettenis@ jsg@ deraadt@
|