| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
need to be root
ok miod
|
| | |
|
| |
|
|
| |
Tested and ok armani@
|
| |
|
|
| |
goal of eventually refactoring them)
|
| |
|
|
| |
halex, rpe, and todd cleared the way for this.
|
| |
|
|
|
| |
Yes, this is stupid, but MI installboot later will make the problem
go away. Until then..
|
| |
|
|
|
| |
run this as root.
ok millert, also discussed with guenther
|
| |
|
|
| |
Diff from Navan Carson via tech@
|
| |
|
|
|
| |
fall back to showing Nd rather than not showing anything.
Issue reported by jmc@.
|
| |
|
|
| |
Cluestick applied by joerg at NetBSD.
|
| |
|
|
| |
ok stsp@ kettenis@
|
| |
|
|
|
|
|
| |
when this can be used.
tweaks ian@
OK ratchov@, sthen@
seems more useful to millert@
|
| |
|
|
| |
now). Reported by landry.
|
| | |
|
| |
|
|
| |
ok miod@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
intervals from src/sbin/ping/ping.c r1.115.
> use clock_gettime(CLOCK_MONOTONIC) to get timestamps to measure the
> interval between sending a ping and getting a reply for it.
>
> this makes it resistant against local wall clock changes, which can
> skew the intervals reported or make them go negative.
this version puts clock_getting in a local gettime() function that
converts to a struct timeval that all the previous callers of
gettimeofday expect to get.
requested by deraadt@ florian@
|
| |
|
|
|
|
|
|
|
|
| |
> use clock_gettime(CLOCK_MONOTONIC) to get timestamps to measure the
> interval between sending a ping and getting a reply for it.
>
> this makes it resistant against local wall clock changes, which can
> skew the intervals reported or make them go negative.
requested by deraadt@ florian@
|
| |
|
|
|
|
|
|
|
|
| |
interval between sending a ping and getting a reply for it.
this makes it resistant against local wall clock changes, which can
skew the intervals reported or make them go negative.
ok deraadt@ florian@
makes sense to lots of others
|
| |
|
|
| |
rev 1.207
|
| |
|
|
| |
and zone xfers. OK florian@ deraadt@
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
pv lists with a mutex. Rearange some code to avoid sleeping/spinning with
one of these locks held, and also take care that we don't allocate/free
any memory in that case. This should make pmap_enter(9), pmap_remove(9) and
pmap_page_protect(9) safe to use without holding the kernel lock.
Other architectures will follow.
ok mlarkin@, deraadt@
|
| |
|
|
|
|
|
| |
use case.
sthen@ noticed a problem with missing records on shutdown.
OK sthen@
|
| |
|
|
| |
Tested and ok sthen@, ok dlg@
|
| |
|
|
|
| |
all required by POSIX. So don't compare it against against
an unsigned constant.
|
| |
|
|
|
| |
No functional change for now, but more robust in case anybody should
ever add additional child processes.
|
| |
|
|
| |
ok dlg@, kettenis@
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When using a pager and the first manual shown is gzip'ed,
the gunzip(1) process ended up as a child of the pager process
such that the man(1) process couldn't wait for it, preventing
proper display of the manual.
Solve this by making the pager a child of the man(1) process
(instead of the other way round), which requires being a bit
more careful about properly closing file descriptors after use
and waiting for the pager before exiting man(1).
|
| |
|
|
|
|
| |
From Zhihao Yuan.
ok millert@ miod@
|
| |
|
|
| |
For example, gcc 4.7 wants this with -Wall. Patch from kristaps@.
|
| |
|
|
| |
some serious shit.
|
| |
|
|
| |
starting with an enormous pile of worm at the start.
|
| |
|
|
|
|
|
| |
is not set; this used to be the case but got broken in 1.113.
Fixes
pciide0 at pci0 dev 2 function 0 "Acard ATP865-R" rev 0x07: DMA
on armish (I/O Data).
|
| |
|
|
|
|
|
|
|
| |
RFC 4941 says in 3.3.5:
"In particular, an implementation MUST NOT create a temporary address
with a zero Preferred Lifetime."
OK sthen, henning, benno
|
| |
|
|
|
|
| |
man(7) always prints a blank line, mdoc(7) doesn't.
Problem in mdoc(7) reported by kristaps@.
mdoc(7) part of the patch tested by kristaps@.
|
| |
|
|
| |
Instead, use the same logic as for man(7).
|
| | |
|
| |
|
|
|
| |
such that that line isn't output with unlimited width.
Problem reported and fix OK by kristaps@.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
OK krw@ benno@
Based on revision 1.66 of usr.sbin/httpd/parse.y:
Make httpd TLSv1.2-only by default. Some older browsers, like IE 10,
will be incompatible with this change. We do this early in the
release cycle, so there is a good chance to get more experience with
the impact of it and the upcoming restricted cipher modes.
OK jsing@ deraadt@ benno@ bmercer@ krw@ florian@
|
| |
|
|
| |
Figured out sthen@
|
| |
|
|
|
|
|
|
| |
will be incompatible with this change. We do this early in the
release cycle, so there is a good chance to get more experience with
the impact of it and the upcoming restricted cipher modes.
OK jsing@ deraadt@ benno@ bmercer@ krw@ florian@
|
| |
|
|
|
|
| |
change in dependencies: shared library versions, and explicit version
requirements in dependencies.
as discussed with aja@ before the lock.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
mpsafe. Most (all?) other architectures now use pools for this, including
non-direct pmap architetcures like sparc and sparc64. Use a special back-end
allocator for pool pages to solve bootstrapping problems. This back-end
allocator allocates the initial pages from kernel_map, switching to the
uvm_km_page allocator once the pmap has been fully initialized. The old
pv entry allocator allocated pages from kmem_map. Using the uvm_km_page
allocator avoids certain locking issues, but might change behaviour under
kva pressure. Time will tell if that's a good or a bad thing.
ok mlarkin@, deraadt@
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Prevent an archive from esacaping the current directory by itself:
when extracting a symlink whose value is absolute or contains ".."
components, just create a zero-length normal file (with additional
tracking of the mode and hardlinks to the symlink) until everything
else is extracted, then go back and replace it with the requested
link (if it's still that zero-length placeholder).
* For tar without -P, if a path in the archive has any ".." components
then strip everything up to and including the last of them (if
it ends in ".." then it becomes ".")
This mostly follows GNU tar's behavior, except for 'tar tf' and
'tar xvf' we report the modified path that would be/was actually
created instead of the raw path from the archive
Above two fixes prompted by a report from Daniel Cegielka
(daniel.cegielka (at) gmail.com)
* For directories whose times or mode will be fixed up in the
clean-up pass, record their dev+ino and then use
open(O_DIRECTORY)+fstat() to verify that we're updating the correct
directory before using futimens() and fchmod().
* Correct buffer overflow in handling of pax extension headers,
caught by the memcpy() overlap check.
previously ok millert@ deraadt@
|
| |
|
|
| |
okay millert@ miod@
|
| |
|
|
|
|
|
| |
Pointed out by Kor son of Rynar (sic) when trying to test
some debug code.
ok matthew@
|
| |
|
|
|
| |
by a similar BoringSSL change, but raising the limit to 1024 bits.
ok jsing@ markus@ guenther@ deraadt@
|