| Age | Commit message (Collapse) | Author |
|---|
|
OBJ_NAME_do_all()
|
|
memory; ok kettenis
|
|
media is no longer needed, due to fix in libc/dlfcn/init.c
thanks kettenis and gkoehler
|
|
headers start at a higher address). Using the wrong base address meant
that we were protecting the wrong address range for the malloc internals
which made the code error out now that mimmutable(2) no longer allows an
RW->R transition. Issue found by gkoehler@ who got most of the way
towards a proper fix.
ok deraadt@
|
|
prodding from kettenis
|
|
ok kettenis
|
|
not be allowed upon immutable memory, instead return EPERM.
Some of these ops are not destructive in OpenBSD, but they are destructive
on other systems, so we take the "all ops" are illegal approach.
Related to this, it should not be allowed to minherit(MAP_INHERIT_ZERO)
immutable regions, or vice versa, calling mimmutable() upon MAP_INHERIT_ZERO
regions, because such a range will be zero'd post-fork in the child.
These now also return EPERM.
Adjusting the madvise / msync behaviour upon immutable memory brings us
closer to the behaviour of the mimmutable clone "mseal" being proposed by
google for inclusion in Linux.
ok kettenis
|
|
ok jsg@
|
|
|
|
No change of compiled code: the bug fix in check_match() affects ZLIB_DEBUG
builds only and the Z_ARG macro is unused.
|
|
|
|
|
|
This adds the hidden visibility attribute to functions that are needed in
multiple source files of the library but not part of the public API. This
is technically a major bump, but that decided to be overkill.
discussed with deraadt and millert
|
|
|
|
Since inpcb tables for UDP and Raw IP have been split into IPv4 and
IPv6, assert that INP_IPV6 flag is correct instead of checking it.
While there, give the table variable a nicer name.
OK sashan@ mvs@
|
|
|
|
mutable mapping is not working right, so temporarily bring back the
RW -> R *only* for ramdisk kernels
|
|
MAXDSIZ was cranked to 128GB back in April 2023, but vmd(8) was limiting
VM RAM size to the old value (32GB).
|
|
As specified, don't include the subsecond part if zero and drop trailing
zeros in the subsecond part. ok millert@
|
|
chrome v8_flags variable's placement in bss, and as a workaround made
it possible to demote a mimmutable mapping's permissions from RW to R.
Further mimmutable-related work in libc's malloc created the same
problem, which led to a better design: objects could be placed into
.openbsd.mutable region, and then at runtime their permission and
immutability could be manipulated better. So the RW to R demotion
logic is no longer being used, and now this semantic is being deleted.
ok kettenis
|
|
been deleted.
|
|
|
|
distinguish between them. Pay attention to the apple,dma-range property
that tells us the desired DVA window. Add support for a new BUS_DMA_FIXED
that allows use of bus_dmamap_load_raw(9) to map things at a pre-determined
DVA. This last change is needed for the upcoming Apple KMS driver.
Hopefully that is the only driver that will need this, so don't attempt to
turn this into an MI feature.
ok patrick@
|
|
Also add two 'len2 must be non-negative.'
from upstream
looks good to jmc
|
|
Most of the conversion is simple there is just log_imsg() that can
no longer display the fd since imsg_get_fd() can only be called once.
OK op@
|
|
ok mlarkin@, tobhe@
|
|
extent_alloc_region(9) that uses a pre-allocated region descriptor.
ok patrick@
|
|
It has been made redundant by the introduction of pinsyscalls(2) which
handles all system calls, rather than just 1.
|
|
|
|
Previously, calling any of the mktemp(3) family would pull in
lstat(2), open(2) and mkdir(2). Now, only the necessary system
calls will be reachable from the binary. OK deraadt@ guenther@
|
|
|
|
to assist qwx(4) development. We may remove this code again at some point
in the future.
Multiple Message MSI has some serious design flaws, especially when
combined with the APIC interrupt controller architecture. It was
superseded by MSI-X. Unfortunately qwx(4) does not implement MSI-X.
ok stsp@, deraadt@
|
|
for other generic KMS drivers.
ok jsg@, matthieu@
|
|
|
|
OK deraadt@
|
|
|
|
|
|
can also be remove. Delete the code using it from the one program that
inspects it.
|
|
a reference reaching the execve(2) stub. The new pinsyscalls(2) that
applies to all system calls has made this redundant.
|
|
an execve(2) stub. The new pinsyscalls(2) that applies to all system
calls has made this redundant.
|
|
|
|
This tests and codifies the behaviour of SSL_shutdown() with respect to
SSL_quiet_shutdown() and SSL_set_shutdown(). For now, only the legacy stack
(TLSv1.2) is tested, as there are currently some subtle differences with
the TLSv1.3 stack.
|
|
ok kettenis
|
|
|
|
this solves one probably with an re(4) going away.
|
|
triggered with TCP socket splicing and TSO, and with that fixed, it
works reliably.
tested by hrvoje, jan@, mbuhl@, bluhm@, feedback from jan@ and bluhm@,
ok jan@ mbuhl@ bluhm@
|
|
Many functions for IPv4 call their IPv6 counterpart if INP_IPV6 is
set at the socket's pcb. By using the generic API consistently,
the logic is not in the caller it gets more readable.
OK mvs@
|
|
This approach does not work as LIST_NEXT() of a removed element
does not return NULL. I causes a crash in syzcaller and triggers
kernel diagnostic assertion "vp->v_uvcount == 0" in sys/kern/kern_unveil.c
line 845 during reboot. Unfortunately the backout brings back the
race in fill_file() and fstat(1) may crash the kernel.
Reported-by: syzbot+54fba1c004d7383d5e85@syzkaller.appspotmail.com
|
|
ok miod tb
|
|
|
