summaryrefslogtreecommitdiffstats
path: root/lib/libkvm/kvm_proc.c
diff options
context:
space:
mode:
authormiod <miod@openbsd.org>2006-11-29 12:24:15 +0000
committermiod <miod@openbsd.org>2006-11-29 12:24:15 +0000
commit46718002fd92ad6071bc17d0a8671800e19e703e (patch)
treec3e4d563248952d16989ab42dacbccaf45ff4422 /lib/libkvm/kvm_proc.c
parentAdd an alignment parameter to uvm_km_alloc1(), and change all callers to (diff)
downloadwireguard-openbsd-46718002fd92ad6071bc17d0a8671800e19e703e.tar.xz
wireguard-openbsd-46718002fd92ad6071bc17d0a8671800e19e703e.zip
Kernel stack can be swapped. This means that stuff that's on the stack
should never be referenced outside the context of the process to which this stack belongs unless we do the PHOLD/PRELE dance. Loads of code doesn't follow the rules here. Instead of trying to track down all offenders and fix this hairy situation, it makes much more sense to not swap kernel stacks. From art@, tested by many some time ago.
Diffstat (limited to 'lib/libkvm/kvm_proc.c')
0 files changed, 0 insertions, 0 deletions