Age | Commit message (Collapse) | Author |
|
Tested by florian on 7260, claudio and myself on 8265, and mlarkin on 9560.
This time even florian's 7260 device seems to be happy.
ok claudio@
|
|
Ensure that io to a file backing a vnd is IO_SYNC, so IO to a
vnd device is both synchronous and not cached in the buffer cache.
This allows the "mount" regress to work repeatably, and avoids
a situation where when the buffer cache cleaner runs to clear
dirty buffers while people are waiting, it actually increases the
dirty buffers when the writes to the underlying vnd are also
delayed.
ok bluhm@
|
|
|
|
Enable them, as all of them pass.
|
|
|
|
ok bluhm@
|
|
|
|
we don't support in LibreSSL and make sure we run as many tests as
possible.
|
|
Fixes a possible crash when a new file structure is added in the
time-out processing code-path.
|
|
for channel ids so the INT_MAX check still makes sense.
|
|
> commit 437896dcafc67d9596774c3bb9f97bfdb4810bb1
> Author: pedro martelletto <pedro@yubico.com>
> Date: Wed Nov 20 09:38:22 2019 +0100
>
> man: mop up dangling .Xr's; Jason McIntyre <jmc@openbsd.org>
|
|
handlers in child process; spotted via weird regress failures in
portable
|
|
|
|
|
|
left over from the type conversion. Noted by t-hashida@amiya.co.jp in
bz#3098, ok markus@ djm@
|
|
mdoc style input jmc
no objections kettenis
|
|
|
|
OK benno@
|
|
known through the imsg lenght.
OK benno@
|
|
|
|
be used by kernel and ld.so in the near future. Adding the system call
earlier will reduce the number of people who try to build through and
encounter agony.
ok kettenis guenther
|
|
|
|
exactly like the ABS{32,64} relocation there.
noted by and ok kettenis@
|
|
tested against openssl 1.1's server.
ok jsing@ tb@
|
|
|
|
This will allow us to test U2F/FIDO2 support in OpenSSH without
requiring real hardware.
ok markus@
|
|
that handle a dozen relocation types for each, just have a nice little switch
for the four specific relocations that actually occur.
Besides being smaller and easier to understand, this fixes the COPY
relocation handling to only do one symbol lookup, instead of looking
up the symbol and then immediately looking it up again (with the
correct flags to find the instance it needs).
ok kettenis@
|
|
Change the printf into a log and only under IFF_DEBUG to reduce dmesg spam.
Loudly requested by beck@ OK deraadt@
|
|
from chohag
|
|
|
|
|
|
Discovered by and ok tim@
|
|
scsi_do_mode_sense(). Just update the values when valid data is
available. Initialize the variables passed to scsi_do_mode_sense() in
the one instance where they weren't already set.
Fixes issue with softraid crypto volumes on 4K-sector disks.
Found, fix tested, and ok tim@
|
|
original diff from Ryan Kavanagh <rak@debian.org>, slightly rearranged
|
|
diff from fgma on github
|
|
any implicit behavior
ok eric@, kn@
|
|
No object change
OK sashan
|
|
Avoid an extra parameter and set NULL initialised conffile conditionally.
From Matthew Martin <phy1729 at gmail dot com>, thanks!
|
|
dereferenced. But there is no boot disk when EFI bootloader has
been received via TFPT. Fake a disk info that never maches a real
disk. Fixes a hang in run_loadfile() during HP Elitebook UEFI boot.
OK patrick@
|
|
the problem was introduced with a "mechanical" patch, which
replaced all "breaks;" with "PF_UNLOCK(); break;" This is wrong
for case of DIOCGETRULESETS.
issue analyzed and patch created by Joerg Goltermann <jg@osn.de>
OK tb@
|
|
wrapped line.
No code change.
|
|
|
|
No code change.
|
|
Default /etc/unwind.conf is optional and may be missing, but explicitly
specified files should exist.
OK florian
|
|
#0 0x000004c27b9051a9 in udp_process_slice (fd=<optimized out>,
event=<optimized out>, v_sc=0x4c55279f500)
at /usr/src/usr.bin/tcpbench/tcpbench.c:606
606 pps = (sc->udp_slice_pkts * 1000) / since_last;
(gdb) p since_last
$1 = 0
ok benno@
|
|
|
|
Tested by mlarkin@ on 9560 and myself on 8265.
ok mlarkin@
|
|
|
|
Rebase the timeout wheel on the system uptime clock. Timeouts are now
set to run at or after an absolute time as returned by nanouptime(9).
Timeouts are thus "tickless": they expire at a real time on that clock
instead of at a particular value of the global "ticks" variable.
To facilitate this change the timeout struct's .to_time member becomes a
timespec. Hashing timeouts into a bucket on the wheel changes slightly:
we build a 32-bit hash with 25 bits of seconds (.tv_sec) and 7 bits of
subseconds (.tv_nsec). 7 bits of subseconds means the width of the
lowest wheel level is now 2 seconds on all platforms and each bucket in
that lowest level corresponds to 1/128 seconds on the uptime clock.
These values were chosen to closely align with the current 100hz
hardclock(9) typical on almost all of our platforms. At 100hz a bucket
is currently ~1/100 seconds wide on the lowest level and the lowest
level itself is ~2.56 seconds wide. Not a huge change, but a change
nonetheless.
Because a bucket no longer corresponds to a single tick more than one
bucket may be dumped during an average timeout_hardclock_update() call.
On 100hz platforms you now dump ~2 buckets. On 64hz machines (sh) you
dump ~4 buckets. On 1024hz machines (alpha) you dump only 1 bucket,
but you are doing extra work in softclock() to reschedule timeouts
that aren't due yet.
To avoid changing current behavior all timeout_add*(9) interfaces
convert their timeout interval into ticks, compute an equivalent
timespec interval, and then add that interval to the timestamp of
the most recent timeout_hardclock_update() call to determine an
absolute deadline. So all current timeouts still "use" ticks,
but the ticks are faked in the timeout layer.
A new interface, timeout_at_ts(9), is introduced here to bypass this
backwardly compatible behavior. It will be used in subsequent diffs
to add absolute timeout support for userland and to clean up some of
the messier parts of kernel timekeeping, especially at the syscall
layer.
Because timeouts are based against the uptime clock they are subject to
NTP adjustment via adjtime(2) and adjfreq(2). Unless you have a crazy
adjfreq(2) adjustment set this will not change the expiration behavior
of your timeouts.
Tons of design feedback from mpi@, visa@, guenther@, and kettenis@.
Additional amd64 testing from anton@ and visa@. Octeon testing from visa@.
macppc testing from me.
Positive feedback from deraadt@, ok visa@
|
|
objects and it running out of memory in the "building shared LLVM library"
stage (at least on i386).
building standard LLVM library
building shared LLVM library (version 1.0)
cc -shared -Wl,-soname,libLLVM.so.1.0 -fpic -o libLLVM.so.1.0 `echo AMDGPUAsmParser.so AMDGPUInstPrinter.so AMDGPUAliasAnalysis.so AMDGPUAlwaysInlinePass.so AMDGPUAnnotateKernelFeatures.so AMDGPUAnnotateUniformValues.so AMDGPUArgumentUsageInfo.so [...snip lots of .so...] ThinLTOBitcodeWriter.so WholeProgramDevirt.so | tr ' ' '\n' | sort -R` -Wl,--start-group -Wl,--end-group
LLVM ERROR: out of memory
cc: error: unable to execute command: Abort trap
cc: error: linker command failed due to signal (use -v to see invocation)
ar: libLLVM.a: No space left on device
*** Error 1 in gnu/usr.bin/clang/libLLVM (<bsd.lib.mk>:193 'libLLVM.a': @ar cqD libLLVM.a `lorder AMDGPUAsmParser.o AMDGPUIn
stPrinter.o AMDG...)
*** Error 254 (<bsd.lib.mk>:225 'libLLVM.so.1.0')
|