OpenBSD cvs log

created 2019-07-03T22:39:01Z
begin 2019-06-22T00:00:00Z
end 2019-06-23T00:00:00Z
path src/sys
commits 9

date 2019-06-22T06:48:25Z
author semarie
files src/sys/kern/sys_generic.c log diff annotate
src/sys/kern/sys_pipe.c log diff annotate
src/sys/kern/vfs_vnops.c log diff annotate
src/sys/sys/file.h log diff annotate
message push the KERNEL_LOCK deeper on read(2) and write(2)

unlocks read(2) and write(2) syscalls families, and push the KERNEL_LOCK
deeper in the code path. KERNEL_LOCK is managed per file type in fileops
handlers (fo_read, fo_write, and fo_close). read(2) and write(2) on
socket are KERNEL_LOCK-free.

initial work from mpi@ and ians@

ok mpi@ kettenis@ visa@ ians@

date 2019-06-22T06:49:14Z
author semarie
files src/sys/kern/syscalls.master log diff annotate
message push the KERNEL_LOCK deeper on read(2) and write(2)

unlocks read(2) and write(2) syscalls families, and push the KERNEL_LOCK
deeper in the code path. KERNEL_LOCK is managed per file type in fileops
handlers (fo_read, fo_write, and fo_close). read(2) and write(2) on
socket are KERNEL_LOCK-free.

initial work from mpi@ and ians@

ok mpi@ kettenis@ visa@ ians@

date 2019-06-22T06:51:45Z
author semarie
files src/sys/sys/syscall.h log diff annotate
src/sys/sys/syscallargs.h log diff annotate
message push the KERNEL_LOCK deeper on read(2) and write(2)

unlocks read(2) and write(2) syscalls families, and push the KERNEL_LOCK
deeper in the code path. KERNEL_LOCK is managed per file type in fileops
handlers (fo_read, fo_write, and fo_close). read(2) and write(2) on
socket are KERNEL_LOCK-free.

initial work from mpi@ and ians@

ok mpi@ kettenis@ visa@ ians@

date 2019-06-22T06:51:46Z
author semarie
files src/sys/kern/init_sysent.c log diff annotate
src/sys/kern/syscalls.c log diff annotate
message push the KERNEL_LOCK deeper on read(2) and write(2)

unlocks read(2) and write(2) syscalls families, and push the KERNEL_LOCK
deeper in the code path. KERNEL_LOCK is managed per file type in fileops
handlers (fo_read, fo_write, and fo_close). read(2) and write(2) on
socket are KERNEL_LOCK-free.

initial work from mpi@ and ians@

ok mpi@ kettenis@ visa@ ians@

date 2019-06-22T08:36:55Z
author jmatthew
files src/sys/dev/pci/if_mcx.c log diff annotate
message Set if_link_state based on the PAOS port register, and update it when
we get a port change event.

ok dlg@

date 2019-06-22T10:14:30Z
author kn
files src/sys/net/if_spppsubr.c log diff annotate
message Remove duplicate initialisation

OK claudio semarie

date 2019-06-22T10:16:14Z
author kn
files src/sys/net/if_spppsubr.c log diff annotate
message Revert accidentially committed hunk from previous

date 2019-06-22T20:15:09Z
author kn
files src/sys/net/if_spppsubr.c log diff annotate
message Make computation of re-challenge timeout more obvious

Instead of masking the difference between lower and upper bound to yield
a random summand that fits, instruct the API to limit their result
accordingly. 0x01fe = 510 = 810 - 300.

arc4random_uniform(upper_bound) returns `upper_bound - 1' as maximum, so
add one to make 810 a possible value for `i'.

OK deraadt

date 2019-06-22T20:30:42Z
author kn
files src/sys/arch/sparc64/dev/beep.c log diff annotate
src/sys/arch/sparc64/dev/beeper.c log diff annotate
message Use timeout_add_msec(9)

hz can simply be reduced has the code wants to wait
(period * hz) / 1000 [ticks] = period / 1000 [s] = period [ms].

With the zero check, this perfectly matches the millisecond version.

This conversion by itself also lifts the implicit expection of the period
to be evenly divisible by ten; in case it was not, integer division
would truncate it.

See /sys/wscons/wskbd.c for how the period is set up.

OK mpi