OpenBSD cvs log

created 2020-07-28T21:05:28Z
begin 2020-05-13T00:00:00Z
end 2020-05-14T00:00:00Z
path src/sys
commits 6

date 2020-05-13T00:48:06Z
author dlg
files src/sys/net/if_tun.c log diff annotate
message only pass the IO_NDELAY flag to ifq_deq_sleep as the nbio argument.

date 2020-05-13T08:10:03Z
author mpi
files src/sys/arch/arm64/arm64/conf.c log diff annotate
src/sys/arch/luna88k/include/conf.h log diff annotate
src/sys/arch/sparc64/include/conf.h log diff annotate
src/sys/sys/conf.h log diff annotate
message Match direct `seltrue' usages with a corresponding `seltrue_kqfilter'.

This ensure spec_kqfilter() won't return an error when spec_poll()
returns success for a given device.

ok visa@

date 2020-05-13T08:13:42Z
author mpi
files src/sys/dev/usb/ugen.c log diff annotate
src/sys/dev/usb/uhid.c log diff annotate
src/sys/miscfs/fuse/fuse_device.c log diff annotate
message Use seltrue_kqfilter() instead of hand-rolling it in multiple drivers.

ok visa@

date 2020-05-13T08:32:43Z
author mpi
files src/sys/arch/amd64/amd64/conf.c log diff annotate
src/sys/arch/amd64/include/conf.h log diff annotate
src/sys/arch/i386/i386/conf.c log diff annotate
src/sys/arch/i386/include/conf.h log diff annotate
message Kill biospoll/pctrpoll defines and use `seltrue' directly in cdev_*_init().

While here use the kqfilter equivalent to `seltrue' to ensure both
interfaces are coherent.

ok visa@

date 2020-05-13T17:31:16Z
author cheloha
files src/sys/dev/sdmmc/sdhc.c log diff annotate
src/sys/dev/sdmmc/sdmmc.c log diff annotate
message sdhc(4), sdmmc(4): tsleep(9) -> tsleep_nsec(9); ok patrick@

date 2020-05-13T21:34:37Z
author cheloha
files src/sys/net/bpf.c log diff annotate
src/sys/net/bpfdesc.h log diff annotate
message bpf(4): separate descriptor non-blocking status from read timeout

If you set FIONBIO on a bpf(4) descriptor you enable non-blocking mode
and also clobber any read timeout set for the descriptor. The reverse
is also true: do BIOCSRTIMEOUT and you'll set a timeout and
simultaneously disable non-blocking status. The two are mutually

This relationship is undocumented and might cause a bug. At the
very least it makes reasoning about the code difficult.

This patch adds a new member to bpf_d, bd_rnonblock, to store the
non-blocking status of the descriptor. The read timeout is still
kept in bd_rtout.

With this in place, non-blocking status and the read timeout can
coexist. Setting one state does not clear the other, and vice versa.

Separating the two states also clears the way for changing the bpf(4)
read timeout to use the system clock instead of ticks. More on that
in a later patch.

With insight from dlg@ regarding the purpose of the read timeout.

ok dlg@