OpenBSD cvs log

created 2019-06-08T11:05:30Z
begin 2019-06-01T00:00:00Z
end 2019-06-02T00:00:00Z
path src/sys
commits 10

date 2019-06-01T00:02:28Z
author jsg
files src/sys/dev/pci/drm/drm_file.c log diff annotate
message drm: Wake up next in drm_read() chain if we are forced to putback the event

From Chris Wilson
00734a9e7329acc48e575f697ee4118998c1dac0 in linux 4.19.y/4.19.47
60b801999c48b6c1dd04e653a38e2e613664264e in mainline linux

date 2019-06-01T04:30:52Z
author jsg
files src/sys/arch/arm64/arm64/cpu.c log diff annotate
message Recognise Cortex-A65.
ok kettenis@

date 2019-06-01T11:39:57Z
author jca
files src/sys/lib/libz/infback.c log diff annotate
src/sys/lib/libz/inffast.c log diff annotate
src/sys/lib/libz/inflate.c log diff annotate
message Fix warnings when building zlib with ZLIB_CONST defined

Probably not very useful (given the lack of feedback) but feels more
correct. Kernel part tested with option ZLIB_CONST.

date 2019-06-01T11:45:01Z
author kettenis
files src/sys/arch/arm64/arm64/machdep.c log diff annotate
src/sys/arch/arm64/arm64/pmap.c log diff annotate
message On machines with large amounts of physical memory we fail to initialize uvm
because we don't have enough kernel memory available in the early bootstrap
phase to allocate the vm_page structures. Fix this by making uvm_growkernel()
work before uvm is initialized like we do on other architectures that don't
use a direct map and explicitly call it after enumerating the available
physical memory with an estimate of how much KVA we need to initialize uvm.

ok patrick@

date 2019-06-01T14:11:17Z
author mpi
files src/sys/kern/init_main.c log diff annotate
src/sys/kern/kern_acct.c log diff annotate
src/sys/kern/kern_exec.c log diff annotate
src/sys/kern/kern_exit.c log diff annotate
src/sys/kern/kern_fork.c log diff annotate
src/sys/kern/kern_resource.c log diff annotate
src/sys/kern/kern_sched.c log diff annotate
src/sys/kern/kern_sysctl.c log diff annotate
src/sys/kern/kern_time.c log diff annotate
src/sys/kern/sched_bsd.c log diff annotate
src/sys/kern/tty.c log diff annotate
message Revert to using the SCHED_LOCK() to protect time accounting.

It currently creates a lock ordering problem because SCHED_LOCK() is taken
by hardclock(). That means the "priorities" of a thread should be moved
out of the SCHED_LOCK() first in order to make progress.

Reported-by: syzbot+8e4863b3dde88eb706dc@syzkaller.appspotmail.com
via anton@ as well as by kettenis@

date 2019-06-01T14:11:18Z
author mpi
files src/sys/sys/proc.h log diff annotate
src/sys/sys/resourcevar.h log diff annotate
src/sys/sys/sysctl.h log diff annotate
message Revert to using the SCHED_LOCK() to protect time accounting.

It currently creates a lock ordering problem because SCHED_LOCK() is taken
by hardclock(). That means the "priorities" of a thread should be moved
out of the SCHED_LOCK() first in order to make progress.

Reported-by: syzbot+8e4863b3dde88eb706dc@syzkaller.appspotmail.com
via anton@ as well as by kettenis@

date 2019-06-01T18:38:27Z
author patrick
files src/sys/arch/arm64/include/vmparam.h log diff annotate
message Bump VM_MAX_KERNEL_ADDRESS so that we have about 16G of KVA. Since
we need KVA to keep track of all the RAM pages, machines with a lot
of memory easily exhaust our KVA space. We need about 1G of KVA
per 32G of memory, so with 16G of KVA we can maintain close to 512G
of memory.

ok kettenis@

date 2019-06-01T22:42:18Z
author deraadt
files src/sys/sys/proc.h log diff annotate
src/sys/sys/syscall_mi.h log diff annotate
message Refactor the MAP_STACK feature, and introduce another similar variation:
Lookup the address that a syscall instruction is executed from, and kill
the process if that page is writeable. This brings an aspect of W^X
behaviour to W|X mappings (in JITs not yet adapted to W^X). The goal is
to remove simple attack methods and force use of ret2libc or other more
complicated means.
ok kettenis stefan visa

date 2019-06-01T22:42:20Z
author deraadt
files src/sys/arch/alpha/alpha/trap.c log diff annotate
src/sys/arch/amd64/amd64/trap.c log diff annotate
src/sys/arch/arm/arm/fault.c log diff annotate
src/sys/arch/arm64/arm64/trap.c log diff annotate
src/sys/arch/hppa/hppa/trap.c log diff annotate
src/sys/uvm/uvm_map.c log diff annotate
src/sys/uvm/uvm_map.h log diff annotate
message Refactor the MAP_STACK feature, and introduce another similar variation:
Lookup the address that a syscall instruction is executed from, and kill
the process if that page is writeable. This brings an aspect of W^X
behaviour to W|X mappings (in JITs not yet adapted to W^X). The goal is
to remove simple attack methods and force use of ret2libc or other more
complicated means.
ok kettenis stefan visa

date 2019-06-01T22:42:21Z
author deraadt
files src/sys/arch/i386/i386/trap.c log diff annotate
src/sys/arch/mips64/mips64/trap.c log diff annotate
src/sys/arch/powerpc/powerpc/trap.c log diff annotate
src/sys/arch/sparc64/sparc64/trap.c log diff annotate
message Refactor the MAP_STACK feature, and introduce another similar variation:
Lookup the address that a syscall instruction is executed from, and kill
the process if that page is writeable. This brings an aspect of W^X
behaviour to W|X mappings (in JITs not yet adapted to W^X). The goal is
to remove simple attack methods and force use of ret2libc or other more
complicated means.
ok kettenis stefan visa