Age | Commit message (Collapse) | Author |
|
used and depended, mimicking new changes by guenther to amd64.
|
|
|
|
openbsd_randomize segments. While here, make the 'bsd' target depend on
the ldscript.
problem noted by and ok deraadt@
|
|
tested by and ok jsg@
|
|
|
|
ok deraadt
|
|
internal speaker, line input and hp output. Tested on i386/amd64.
hints/help & ok ratchov@
|
|
This includes a commit made by Andy Polyakov <appro at openssl ! org>
to the OpenSSL source tree on Wed, 28 Jun 2006 with the following
message: "Mitigate cache-collision timing attack on last round."
OK naddy, miod
|
|
just the base permission but the maxprot as well.
ok tedu
|
|
that is executable.
ok tedu kettenis guenther
|
|
show the maxprot available in obreak mappings. (the default remains
PROT_READ | PROT_WRITE, so don't be afraid).
ok tedu
|
|
ok tedu@
|
|
rearrange things in mountswap to delay malloc and always allocate
needed size.
|
|
vmcmd_map_zero() just returns the result of uvm_map(), so make it a tail call
|
|
1. Always unmask the slot context for the "Set Address" command.
2. Use the right spl when submitting a transfer to prevent from
setting up a timer on an already completed xfer.
Analyzed with and ok jsg@
|
|
|
|
required to cast their pointers, which is ugly and possibly error
prone. accidentally casting an int to a pointer, for example, instead
of the address of the int. implicit void * casting is safer.
This updates the kernel hash interfaces to use void *. Similar changes
are possible for userland. I think it's safe, but there may be some
peculiar source compatbility issues there, so let's just do the kernel
first.
ok dlg millert
|
|
|
|
PROT_NONE, PROT_READ, PROT_WRITE, and PROT_EXEC from mman.h.
PROT_MASK is introduced as the one true way of extracting those bits.
Remove UVM_ADV_* wrapper, using the standard names.
ok doug guenther kettenis
|
|
ok phessler@ tedu@
|
|
for NS Saturn based boards.
From NetBSD
ok deraadt@
|
|
in ptsignal(), which broke ptrace() in various circumstances, act more like
sigsuspend() by updating the signal mask and picking off waited for signals
when one occurs. Don't always restart when an unwaited-for-but-handled
signal occurs, as that screws with both timeout calculation and cancellation.
main problem noted by jmatthew@
ok tedu@
|
|
ok deraadt@
|
|
prodded by brad@, ok deraadt@
|
|
|
|
attacks.
this is a textbook use of siphash.
the idea of using siphash for this came from yasuoka-san, but i had
the time to do it. he also tested and tweaked this diff.
ok yasuoka@ mikeb@
|
|
|
|
|
|
ok yasuoka@ mikeb@
|
|
us handle the slowdown where we already give up pr_mtx and gets rid of
an ugly goto.
ok tedu@ who i think has more tweaks coming
|
|
Revert NFS_DIRBLKSIZE back to data. This matches an identical comment
in another part of this file.
|
|
|
|
|
|
|
|
|
|
made possible by the install/upgrade changes by krw and the ifconfig
adjustments by me.
ok krw reyk
|
|
|
|
|
|
testing and ok jsg@
|
|
|
|
has been added to the pool, else it doesn't help because the memory isn't
available. lost in locking rework.
tested blambert sthen
|
|
|
|
|
|
situations where e.g. web browsing is cpu intense but intermittently idle.
subject to further refinement and tuning.
|
|
Pointed out by John-Mark Gurney <jmg at funkthat ! com>, thanks!
|
|
Since there's now no way to select maximum receive unit size the
hardware is programmed to accept frame sizes up to 9216 which is
now the maximum (down from 15.5K since this is supposed to work
in all advanced configurations and gives slightly better flow
control watermark ranges) and split all frames larger 2K into
multiple fragments (code was already there but wasn't enabled).
Tested on 82599 (SFP+) and X540 (10GBaseT).
With input from dlg@.
|
|
This is not necessary, as confirmed by tedu@ and kettenis@.
Solve the major contention problem seen on my Dual G5. Reduce the
build time of a kernel with two jobs from 5h+ to 18min and expose more
easily pmap/memroy corruptions 8)
ok kettenis@
|
|
changed. This saves a lot of I/O when attaching/detaching devices
and might help with some timing related problems.
Has been in snap for ten days, committing now so that people testing
xhci(4) test the same thing w/ snapshots and their own kernel.
|
|
ok deraadt, guenther
|
|
bugs that panic the kernel and it's unclear if any such device works at all.
Anyone in possession of a working AR9300 device that stops working with this
commit please talk to me. I've only seen evidence of this code not working.
ok kirby@ mpi@ phessler@ dcoppa@
|