wireguard-openbsd/sys/arch/powerpc, branch masterWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/powerpc?h=master2021-03-15T15:49:20ZDon't put an extern variable (ppc_kvm_stolen) into vmparam.h, other instances2021-03-15T15:49:20Zderaadtderaadt@openbsd.org2021-03-15T15:49:20Zurn:sha1:08e7272b46eb3cbeff5e418de069c2be48ef04ab
of this file are only doing cpp #define
spelling2021-03-11T11:16:54Zjsgjsg@openbsd.org2021-03-11T11:16:54Zurn:sha1:36fd90dcf1acf2ddb4ef5dbabe5313b3a8d46ee2pmap_avail_setup() is the only place physmem is calculated, delete a bunch2021-03-10T07:28:19Zderaadtderaadt@openbsd.org2021-03-10T07:28:19Zurn:sha1:14f9a22138b8eef9eaa876a7449bec53dd8f7d89
of code which thinks it could be done elsewhere.
ok kurt
Add retguard to macppc kernel locore.S, ofwreal.S, setjmp.S2020-11-28T19:49:30Zgkoehlergkoehler@openbsd.org2020-11-28T19:49:30Zurn:sha1:15572fcf8c6bfa0588565cd23f393a5a1499ea57
This changes RETGUARD_SETUP(ffs) to RETGUARD_SETUP(ffs, %r11, %r12)
and RETGUARD_CHECK(ffs) to RETGUARD_CHECK(ffs, %r11, %r12)
to show that r11 and r12 are in use between setup and check, and to
pick registers other than r11 and r12 in some kernel functions.
ok mortimer@ deraadt@
uvm_grow() no longer needs the KERNEL_LOCK, bring it back to just2020-10-27T19:18:05Zderaadtderaadt@openbsd.org2020-10-27T19:18:05Zurn:sha1:7598ed2842b152b5e3ad2f077f25d95d298b2eff
around uvm_fault(), and slightly refactor code to be more like on
other architectures
Retguard asm macros for powerpc libc, ld.so2020-10-26T22:07:05Zgkoehlergkoehler@openbsd.org2020-10-26T22:07:05Zurn:sha1:d2c5a4743fb945f45b034a3a830a96f7e1bc695d
Add retguard to some, but not all, asm functions in libc. Edit SYS.h
in libc to remove the PREFIX macros and add SYSENTRY (more like
aarch64 and powerpc64), so we can insert RETGUARD_SETUP after
SYSENTRY. Some .S files in this commit don't get retguard, but do
stop using the old prefix macros.
Tested by deraadt@, who put this diff in a macppc snap.
mi_ast() should not use the old cpu, but the cpu (after potential sleep2020-09-24T20:22:50Zderaadtderaadt@openbsd.org2020-09-24T20:22:50Zurn:sha1:279d7224b89de8f9b23b5bf98fc8f2b6a1ba151e
in refreshcreds()
ok kettenis
Only perform uvm_map_inentry() checks for PROC_SP for userland pagefaults.2020-09-24T17:54:28Zderaadtderaadt@openbsd.org2020-09-24T17:54:28Zurn:sha1:5e7211b0919c7cc85a1047c9978675dc186d7e71
This should be sufficient for identifying pivoted ROP. Doing so for other
traps is at best opportunistic for finding a straight-running ROP chain,
but the added (and rare) sleeping point has proven to be dangerous.
Discussed at length with kettenis and mortimer.
ok mortimer kettenis mpi
Include <sys/systm.h> directly instead of relying on hidden UVM includes.2020-09-11T09:27:09Zmpimpi@openbsd.org2020-09-11T09:27:09Zurn:sha1:311b6aa824a006e2f436474d9ba54b31c6d40a20
The header is being pulled via db_machdep.h -> uvm_extern.h -> uvm_map.h
Push KERNEL_LOCK/UNLOCK() dance inside trapsignal().2020-08-19T10:10:57Zmpimpi@openbsd.org2020-08-19T10:10:57Zurn:sha1:726a21b09a68545ce072963e07cac351d5fdc85b
ok kettenis@, visa@