wireguard-openbsd/libexec, branch masterWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/libexec?h=master2021-03-16T18:03:06ZOn i386 don't attempt to map shared libraries in low memory when2021-03-16T18:03:06Zkurtkurt@openbsd.org2021-03-16T18:03:06Zurn:sha1:0458707b7ef7291748979ef4c9b23cab3a6812ff
a large executable's .text section crosses the 512MB exec line.
Executables that have MAXTSIZ > 64MB can map above the default
512MB exec line. When this happens, shared libs that attempt to map
into low memory will find their .data section can not be mapped. ld.so
will attempt to remap the share lib at higher addresses until it can be
mapped. For very large executables like chrome this process is very
time consuming. This change detects how much of the executable's
.text section exceeds 512MB and uses that as the initial hint for
shared libs to map into which avoids attempting to map into blocked
memory.
okay deraadt@
Check auth_mkvalue(3) return value for NULL (malloc failure).2021-01-02T20:32:20Zmillertmillert@openbsd.org2021-01-02T20:32:20Zurn:sha1:07817e4bdc8b6868189ab279749fa0d1c77e97fb
For constant strings we don't actually need to use auth_mkvalue(3).
Problem reported by Ross L Richardson.
We know about optreset from unistd.h.2020-12-27T15:11:04Zflorianflorian@openbsd.org2020-12-27T15:11:04Zurn:sha1:f06172036150138dcae26d68a3531f0cba729ca9
From Jan Stary, thanks.
OK martijn
Fix a nasty mem leak in ld.so's own malloc. This was hard to diagnose, since2020-12-26T13:17:33Zottootto@openbsd.org2020-12-26T13:17:33Zurn:sha1:e85425675158b0b3305d1dde748135080ca0b921
malloc dumping and gdb do not help at all when studying ld.so. In the end
it turns out ot be a simple merge error causing extra mmap calls.
ok miller@ tb@
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@
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.
Use the retguard macros from asm.h to protect the system call stubs.2020-10-16T23:42:53Zderaadtderaadt@openbsd.org2020-10-16T23:42:53Zurn:sha1:ac44ab0d128055f2f7e7b4411beb86f83c6eb8ff
ok mortimer kettenis
make three mib[] arrays const, as was done in libc2020-10-15T04:12:43Zderaadtderaadt@openbsd.org2020-10-15T04:12:43Zurn:sha1:fa3953dbf8c403a63d907c49154e9f1a9a6d638cDon't skip file systems just because the parent fs is nodev and nosuid.2020-10-11T18:28:17Zmillertmillert@openbsd.org2020-10-11T18:28:17Zurn:sha1:14dbc6804011bf8bc03e02f7e0718c4149b8a1bf
Fixes instances where a mount point uses the nodev and nosuid options
but another file system mounted inside that hierarchy does not.
OK schwarze@
afs, nnpfs, and procfs are no longer supported,2020-09-17T06:51:06Zschwarzeschwarze@openbsd.org2020-09-17T06:51:06Zurn:sha1:352e64a166b7bb06ff5892484e1670bd431699d7
so stop looking for them in mount(8) output;
no functional change intended;
OK millert@