| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Pointed out by Jerome Pinot
|
|
Pointed out by Jerome Pinot
|
|
Pointed out by Jerome Pinot
|
|
Pointed out by Jerome Pinot
|
|
Pointed out by Jerome Pinot
|
|
Pointed out by Jerome Pinot
|
|
input from jmc@
|
|
pointed out by jmc@
|
|
ago.
ok kn, deraadt
|
|
variable and fall back to what stty(1) reports, and it does so with
nroff(1), but it didn't with mandoc(1) because it didn't know how
to pass the desired width to mandoc. Teach it to use "-O width=".
OK afresh1@.
I noticed the unimplemented feature when Andrew Daugherity asked
on tech@ what the point of a certain patch in FreeBSD is (which it
turns out we don't need).
|
|
output in UTF-8 encoding on OpenBSD. The consumer is always mandoc(1)
on OpenBSD, which can always handle UTF-8 input (no matter what LC_CTYPE
is) and which always produces useful output: UTF-8 for LC_CTYPE=*.UTF-8
or ASCII otherwise, in particular for LC_CTYPE=C.
Patch written after afresh1@ reported that "perldoc -oman" output
looked bad in both output modes.
OK afresh1@.
|
|
even when a switch(4) instance requires it to supply it. Cases where this
can happen are: if the copy of the packet recieved from the switch is too
short (source/destination pairs can't be recovered), is non-unicast, or
when switchd has to fall back to flooding traffic.
Factor out the check for short packets, stopping before forwarding
decisions are made if the full packet is needed by the switch. Set the
packet buffer early for cases where it is needed otherwise.
Also replace a few bzero's with memset's.
Diff based on one by guenther@
OK phessler@
|
|
|
|
random data into the buffer that we feed the kernel.
ok deraadt@, mlarkin@
|
|
|
|
|
|
While here, stop describing the default (wrong place to be so specific)
|
|
|
|
region is properly allocated by the firmware.
Move the .bss clearing to locore.S because the section has to be ready
when the stack is taken into use. This additionally makes the
C environment more consistent at the start of mips_init().
|
|
other architectures.
|
|
|
|
like install.sub and sysupgrade(8) do.
|
|
|
|
|
|
|
|
ok jsg@
|
|
|
|
|
|
like install.sub does.
* Only verify the signature once.
* Only checksum the newly downloaded files.
ok florian@
|
|
|
|
With some gritty work up to 254 bytes can be discovered. More details at
https://svnweb.freebsd.org/changeset/base/347066
The impact on OpenBSD is very limited:
1 - such stack bytes can be found in raw-device reads, from group operator.
If you can read the raw disks you can undertake other more powerful actions.
2 - read(2) upon directory fd was disabled July 1997 because I didn't like
how grep * would display garbage and mess up the tty, and applying vis(3)
for just directory reads seemed silly. read(2) was changed to return
0 (EOF). Sep 2016 this was further changed to EISDIR, so you still cannot
see the bad bytes.
3 - In 2013 when guenther adapted the getdents(2) directory-reading system
call to 64-bit ino_t, the userland data format changed to 8-byte-alignment,
making it incompatible with the 4-byte-alignment UFS on-disk format. As
a result of code refactoring the bad bytes were not copied to userland.
Bad bytes will remain in old directories on old filesystems, but nothing makes
those bytes user visible. There will be no errata or syspatch issued. I
urge other systems which do expose the information to userland to issue
errata quickly, since this is a 254 byte infoleak of the stack which is great
for ROP-chain building to attack some other bug. Especially if the kernel
has no layout/link-order randomization ...
ok kettenis jca millert otto ...
|
|
AGP-capable chipsets and probably never will.
|
|
ok patrick@
|
|
prod/ok deraadt
|
|
ok millert otto kettenis
|
|
Should be revisited once logwakeup() is fixed.
|
|
Use splassert_fail() instead, please set kern.splassert to 2 and report
the corresponding stack trace if you see a warning.
ok dlg@
|
|
|
|
ok dlg@
|
|
From Thomas Preston
6e0473633af059a559ce7b4cbaa51e389c94085e in mainline linux
Makes inteldrm(4) work on James Hastings's 'HP Stream Laptop 14-cb1XX'
a Gemini Lake system where finding the VBT fails.
ok kettenis@
|
|
|
|
ok naddy@ florian@
|
|
when we have a serial console by introducing the notion of a "primary"
graphics device. The primary graphics device is the one set up and
used by firmware (BIOS, UEFI).
The goal is to make sure that wsdisplay0 and drm0 reliably attach to
the primary graphics device such that X works out of the box even
if you have multiple cards or if you are using a serial console.
This also fixes the situation where inteldrm(4) or radeondrm(4) would
take over the console on UEFI systems even if the kernel was booted
with a serial console.
ok jsg@
|
|
|
|
From Noralf Tronnes
c5eb9a424ebd2d9f9e3cccdf2bfbb415c2921261 in linux 4.19.y/4.19.39
3f04e0a6cfebf48152ac64502346cdc258811f79 in mainline linux
|
|
controllers, written by dlg@ and me based on the cut down non-NDA
programming reference manual Mellanox were nice enough to release.
ok dlg@ deraadt@
|
|
From Andrew Daugherity <andrew.daugherity () gmail ! com>
Corrections to fix and OK millert@, suggestions and OK schwarze@
|
|
|
