OpenBSD cvs log

created 2024-07-14T13:19:04Z
begin 2024-07-11T00:00:00Z
end 2024-07-12T00:00:00Z
path src/sys
commits 5

date 2024-07-11T07:40:03Z
author deraadt
files src/sys/arch/macppc/stand/ofwboot/Makefile log diff annotate
message umoddi3.c is now needed for libz

date 2024-07-11T12:07:39Z
author kettenis
files src/sys/arch/arm64/arm64/cpu.c log diff annotate
message Use FEAT_RNG to feed entropy into the random subsystem like we do on amd64.

ok patrick@, deraadt@

date 2024-07-11T12:07:40Z
author kettenis
files src/sys/arch/arm64/conf/Makefile.arm64 log diff annotate
message Use FEAT_RNG to feed entropy into the random subsystem like we do on amd64.

ok patrick@, deraadt@

date 2024-07-11T12:39:53Z
author kettenis
files src/sys/dev/pci/drm/include/linux/fb.h log diff annotate
message Turn FBINFO_xxx defines into proper flags. Gets rid of an unwanted
warning introduced by a recent commit to drm_fbdev_dma.c.

ok jsg@

date 2024-07-11T14:11:55Z
author bluhm
files src/sys/kern/kern_sysctl.c log diff annotate
message Use atomic operations to access integers in sysctl(2).

In sysctl_int_bounded() use atomic operations to load, store, or
swap integer values. By using volatile pointers this will result
in a single assembly instruction, no matter how over optimizing
compilers will become. Note that this does not solve data dependency
problems, nor MP problems in the kernel code using these integers.
For full MP safety additional considerations, memory barriers, or
locks will be needed where the values are used. But for simple
integer in- and output volatile is enough. If new and old value
pointers are given to sysctl, atomic swapping guarantees that
userlands sees the same old value only once. There are more
sysctl_int() functions that have to be adapted.

OK deraadt@ kettenis@