| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Even though these chips implement the standard USB CDC class protocol
we need a separate driver to be able to disable hardware flow control.
Hardware flow control is automatically enabled in CDC mode but if the
relevant lines aren't connected this prevents the chip from getting
input.
ok deraadt@
|
|
|
|
ok deraadt@
|
|
parse.y rev 1.381 2019/02/27
ok sthen@
|
|
|
|
cleanup some output.
|
|
users to know the size of the currently used font.
Based on a diff from Artturi Alm, thanks!
OK sthen@, kettenis@, tedu@, jcs@
|
|
enough data). Expects a failure (with errno = ECANCELED).
|
|
|
|
Reported by oss-fuzz, really fixes issue #13805.
ok beck@ tb@
|
|
form tagging and short form length encoding). Add two tests for long form
length encoding.
|
|
|
|
|
|
ok jsing
|
|
cause connection to close incorrectly; Report and patch from Jakub
Jelen in bz#2757; ok dtucker@ markus@
|
|
From Brad
|
|
only two older cards currently attempt to set this, and it
should not be neccessary anyway;
i've added in a some (commented) info to explain this;
discussed with and ok stsp
|
|
|
|
|
|
|
|
Not hooked up to the build.
|
|
of if statements.
|
|
Shorten it to better match the style of other log messages.
ok jca@
|
|
disable this), and provide a little more info on "duration";
some driver-specific notes hopefully to follow...
help/ok stsp
|
|
the guest VM. By default, VMX sets the limits to 0xFFFF on exit, which is
larger than what we want and can lead to security issues.
While here, reset the LDT as well. We don't use this in OpenBSD, and
VMX loads a null LDT selector on exit anyway, but resetting it here
prevents any future surprises.
Pointed out by Maxime Villard from NetBSD - thanks!
ok deraadt@
|
|
(previous commit was for read-side)
|
|
|
|
|
|
|
|
Diagnosed by krw, ok florian
|
|
No other (known) BSD-derived adjtime(2) implementation checks for overflow
when converting delta into its final denomination of fractional seconds.
This is peculiar, as the call originates in 4.3BSD.
However, glibc, uclibc, and (to an extent) musl /do/ check the input and set
EINVAL if it exceeds a certain bound, so we'll just use the errno that they
use to be consistent with extant practice.
Prompted by the comment kettenis@ left when we switched to storing the
adjustment in an int64_t like ~5 years ago (kern_time.c,v 1.87).
Positive feedback from deraadt@, manpage bits ok jmc@,
no code complaints from otto@ or tedu@.
|
|
added aggressively today. Hopefully post release a glorious
flensing will remove UNVEIL_INSPECT anyway
Reported-by: syzbot+3375ce307ac7909b907b@syzkaller.appspotmail.com
|
|
From phrocker via github.
|
|
Otherwise, the system can crash in smr_call_impl() if SMT is
enabled later.
Crash reported by jcs@
|
|
tc_lock allows adjfreq(2) and the kern.timecounter.hardware sysctl(2)
to read/write the active timecounter pointer and the .tc_adj_freq
member of the active timecounter safely. This eliminates any possibility
of a torn read/write for the .tc_adj_freq member when we drop the
KERNEL_LOCK from the timecounting layer. It also ensures the active
timecounter does not change in the midst of an adjfreq(2) call.
Because these are not high-traffic paths, we can get away with using
tc_lock in write-mode to ensure combination read/write adjtime(2) calls
are relatively atomic (a) to other writer adjtime(2) calls, and (b) to
settimeofday(2)/clock_settime(2) calls, which cancel ongoing adjtime(2)
adjustment.
When the KERNEL_LOCK is dropped, an unprivileged user will be able to
create some tc_lock contention via adjfreq(2); it is very unlikely to
ever be a problem. If it ever is actually a problem a lockless read
could be added to address it.
While here, reorganize sys_adjfreq()/sys_adjtime() to minimize code
under the lock. Also while here, make tc_adjfreq() void, as it cannot
fail under any circumstance. Also also while here, annotate various
globals/struct members with lock ordering details.
With lots of input from mpi@ and visa@.
ok visa@
|
|
Match block overrides a more restrictive global default.
Spotted by jmc@, ok markus@
|
|
|
|
|
|
yet. In the meantime, make it a warning-no-op, as most usage cases
will be satisfied by this (and hopefully annoy someone to write support)
ok florian benno
|
|
ok benno@
|
|
Additional code would be needed to support actually changing the
router-id at runtime; for now be consistent and reject the new
configuration to avoid users a "wtf" moment.
From Mitchell Krome, input from benno@ and deraadt@, ok benno@
|
|
ok krw@ millert@
|
|
parts of the status line, from Avi Halachmi.
|
|
- use an IPI to notify other CPUs toi update CR4 and the MSRs
- use the cpu(4) resume callback to restore the pctr(4) settings after
suspend/hibernate
ok kettenis@ deraadt@
|
|
ok kettenis@ deraadt@
|
|
ok tedu sobrado deraadt
|
|
|
|
These are no longer used now that we defer signature algorithm selection.
ok beck@
|
|
ok beck@
|
