fftw3: use fortran module
configure picks up gfortran which may lead to build failures due to junking.
Worse, when building with gfortran, additional public symbols are present
in the fftw3_threads.
fortran module: stop setting USE_NOBTCFI-aarch64
This was necessary for gcc/8 but according to testing by sthen with gcc/15
this is no longer necessary with modern gcc.
update to redis-6.2.23
"A crafted stream `RESTORE` payload can make two consumers share the
same NACK, leading to a use-after-free that may result in Remote Code
Execution"
Kill the uvm_pmalloc mechanism. This never really worked, at least until
kirill@ fixed some page number/address confusement. But it can't really
work since pages freed by the pagedaemon are likely going to be grabbed
by other consumers before we issue a wakeup through the uvm_pmalloc
mechanism. At this point the consensus is that it adds complexity to the
pagedaemon that stands in the way of progress.
Discussed with claudio@ and deraadt@
ok deraadt@
vmd(8): guard firmware config system state with a mutex.
While vmd is not yet SMP, if multiple VCPUs emulate io to the Qemu
firmware config registers simultaneously, they will race in mutating
and observing state.
Report and diff by Andrew Griffiths.
ok hshoexer@
vmd(8): reject GPAs in holes during gpa translation.
vmd independentaly allocates guest memory in a series of ranges,
mirroring the physical memory layout for the guest. The GPA translation
in find_gap_range() incorrectly selects a memory range if the GPA
is in a hole between two guest memory ranges. Make the initial check
that the GPA falls within the bounds of a known memory range instead
of just prior to the end.
Report and diff by Andrew Griffiths.
ok hshoexer@