| created | 2021-05-16T07:39:28Z |
|---|---|
| begin | 2021-05-11T00:00:00Z |
| end | 2021-05-12T00:00:00Z |
| path | src/sys |
| commits | 18 |
| date | 2021-05-11T08:39:32Z | |||
|---|---|---|---|---|
| author | stsp | |||
| files | src/sys/net80211/ieee80211_output.c | log | diff | annotate |
| message |
In hostap mode don't send data frames to nodes which aren't in state ASSOC. Sending data frames to nodes in other states is wrong since the node's data structure might not be set up properly in such states. This could explain occasional "key unset for sw crypto" panics observed with athn(4) hostap interfaces. Problem reported and fix tested by Mikolaj Kucharski. |
|||
| date | 2021-05-11T08:46:31Z | |||
|---|---|---|---|---|
| author | stsp | |||
| files | src/sys/net80211/ieee80211_crypto.c | log | diff | annotate |
| message |
During a "key unset for sw crypto" panic, display more meta-data about the offending key. This will hopefully help with debugging. |
|||
| date | 2021-05-11T11:17:32Z | |||
|---|---|---|---|---|
| author | mvs | |||
| files | src/sys/kern/syscalls.master | log | diff | annotate |
| message |
Unlock bind(2). ok mpi@ |
|||
| date | 2021-05-11T11:18:15Z | |||
|---|---|---|---|---|
| author | mvs | |||
| files | src/sys/kern/init_sysent.c | log | diff | annotate |
| src/sys/kern/syscalls.c | log | diff | annotate | |
| src/sys/sys/syscall.h | log | diff | annotate | |
| src/sys/sys/syscallargs.h | log | diff | annotate | |
| message | regen | |||
| date | 2021-05-11T11:19:10Z | |||
|---|---|---|---|---|
| author | mvs | |||
| files | src/sys/kern/syscalls.master | log | diff | annotate |
| message |
Unlock connect(2). ok mpi@ |
|||
| date | 2021-05-11T11:19:39Z | |||
|---|---|---|---|---|
| author | mvs | |||
| files | src/sys/kern/init_sysent.c | log | diff | annotate |
| src/sys/kern/syscalls.c | log | diff | annotate | |
| src/sys/sys/syscall.h | log | diff | annotate | |
| src/sys/sys/syscallargs.h | log | diff | annotate | |
| message | regen | |||
| date | 2021-05-11T11:20:23Z | |||
|---|---|---|---|---|
| author | mvs | |||
| files | src/sys/kern/syscalls.master | log | diff | annotate |
| message |
Unlock listen(2). ok mpi@ |
|||
| date | 2021-05-11T11:20:51Z | |||
|---|---|---|---|---|
| author | mvs | |||
| files | src/sys/kern/init_sysent.c | log | diff | annotate |
| src/sys/kern/syscalls.c | log | diff | annotate | |
| src/sys/sys/syscall.h | log | diff | annotate | |
| src/sys/sys/syscallargs.h | log | diff | annotate | |
| message | regen | |||
| date | 2021-05-11T11:21:31Z | |||
|---|---|---|---|---|
| author | mvs | |||
| files | src/sys/kern/syscalls.master | log | diff | annotate |
| message |
Unlock shutdown(2). ok mpi@ |
|||
| date | 2021-05-11T11:21:58Z | |||
|---|---|---|---|---|
| author | mvs | |||
| files | src/sys/kern/init_sysent.c | log | diff | annotate |
| src/sys/kern/syscalls.c | log | diff | annotate | |
| src/sys/sys/syscall.h | log | diff | annotate | |
| src/sys/sys/syscallargs.h | log | diff | annotate | |
| message | regen | |||
| date | 2021-05-11T13:25:26Z | |||
|---|---|---|---|---|
| author | patrick | |||
| files | src/sys/arch/arm64/conf/GENERIC | log | diff | annotate |
| src/sys/arch/arm64/conf/RAMDISK | log | diff | annotate | |
| message | Enable iwx(4). | |||
| date | 2021-05-11T13:29:25Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/kern/kern_timeout.c | log | diff | annotate |
| message |
timeout_barrier(9), timeout_del_barrier(9): remove kernel lock In timeout_barrier(9) we take/release the kernel lock to ensure that the given timeout has finished running (if it had been running at all). This approach is inefficient. If we put a barrier timeout on the queue and wait for it to run in cond_wait(9) we can block instead of spinning for the kernel lock. We already do this for process-context timeouts in timeout_barrier(9) anyway. Discussed with dlg@, visa@, and mpi@. ok dlg@ |
|||
| date | 2021-05-11T13:56:28Z | |||
|---|---|---|---|---|
| author | deraadt | |||
| files | src/sys/arch/riscv64/riscv64/locore.S | log | diff | annotate |
| message |
riscv has no delay slots, we don't need anything like this in the sigcode. ok jsg drahn |
|||
| date | 2021-05-11T14:58:08Z | |||
|---|---|---|---|---|
| author | deraadt | |||
| files | src/sys/arch/riscv64/conf/GENERIC | log | diff | annotate |
| src/sys/arch/riscv64/conf/RAMDISK | log | diff | annotate | |
| src/sys/arch/riscv64/dev/plic.c | log | diff | annotate | |
| src/sys/arch/riscv64/dev/plic.h | log | diff | annotate | |
| src/sys/arch/riscv64/dev/riscv_cpu_intc.c | log | diff | annotate | |
| src/sys/arch/riscv64/dev/riscv_cpu_intc.h | log | diff | annotate | |
| src/sys/arch/riscv64/dev/simplebus.c | log | diff | annotate | |
| src/sys/arch/riscv64/include/bootconfig.h | log | diff | annotate | |
| src/sys/arch/riscv64/include/cpu.h | log | diff | annotate | |
| src/sys/arch/riscv64/include/db_machdep.h | log | diff | annotate | |
| src/sys/arch/riscv64/include/intr.h | log | diff | annotate | |
| src/sys/arch/riscv64/include/pmap.h | log | diff | annotate | |
| src/sys/arch/riscv64/include/profile.h | log | diff | annotate | |
| src/sys/arch/riscv64/include/riscvreg.h | log | diff | annotate | |
| src/sys/arch/riscv64/include/softintr.h | log | diff | annotate | |
| src/sys/arch/riscv64/include/vmparam.h | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/conf.c | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/db_disasm.c | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/db_interface.c | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/fpu.c | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/locore.S | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/machdep.c | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/mem.c | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/pmap.c | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/process_machdep.c | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/sig_machdep.c | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/syscall.c | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/trap.c | log | diff | annotate | |
| message | whitespace cleanup | |||
| date | 2021-05-11T14:58:25Z | |||
|---|---|---|---|---|
| author | deraadt | |||
| files | src/sys/arch/riscv64/dev/plic.c | log | diff | annotate |
| src/sys/arch/riscv64/include/ieee.h | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/machdep.c | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/pmap.c | log | diff | annotate | |
| src/sys/arch/riscv64/riscv64/trap.c | log | diff | annotate | |
| message | more whitespace cleanups | |||
| date | 2021-05-11T16:40:57Z | |||
|---|---|---|---|---|
| author | anton | |||
| files | src/sys/dev/usb/uhidpp.c | log | diff | annotate |
| message |
Temporarily release the mutex while calling sensor_task_register() as it might end up sleeping in malloc(). This can only happen if uhidpp is the first one calling the aforementioned routine which causes the sensors task queue to be allocated. Thanks to Justin Yang <linuxjustin at gmail dot com> for the report. |
|||
| date | 2021-05-11T18:21:12Z | |||
|---|---|---|---|---|
| author | kettenis | |||
| files | src/sys/arch/powerpc64/include/pmap.h | log | diff | annotate |
| src/sys/arch/powerpc64/powerpc64/pmap.c | log | diff | annotate | |
| src/sys/arch/powerpc64/powerpc64/trap.c | log | diff | annotate | |
| message |
A Data Segment Interrupt does not indicate whether it was the result of a read or a write fault. Unfortunately that means we can't call uvm_fault(), as we have to pass the right access_type. In particular, passing PROT_READ for write access on a write-only page will fail. Fix this issue by inserting an appropriate SLB entry when a mapping exists at the fault address. A subsequent Data Storage Interrupt will call uvm_fault() to insert a mapping for the page into the page tables. Fixes the sys/kern/fork-exit regress test. Debugging done by bluhm@ and patrick@ ok bluhm@ |
|||
| date | 2021-05-11T22:04:10Z | |||
|---|---|---|---|---|
| author | dv | |||
| files | src/sys/arch/amd64/amd64/vmm.c | log | diff | annotate |
| message |
vmm(4): fix flawed physical cpu tracking logic in svm_run_vcpu Replace the overly complicated logic used to track which CPU we are on in svm_run_vcpu. This fixes an issue where ltr causes a #GP on exit in certain conditions due to referencing the wrong GDT. This was primarily witnessed with NixOS guests that performed a heavy amount of disk io. Reported by Josh Rickmar. Tested by Josh & abieber@. OK mlarkin@. |
|||