OpenBSD cvs log

created 2021-07-11T05:45:25Z
begin 2021-07-09T00:00:00Z
end 2021-07-10T00:00:00Z
path src/sys
commits 18

date 2021-07-09T01:22:05Z
author dlg
files src/sys/net/ifq.c log diff annotate
message ifq_hdatalen can return 0 if ifq_empty is true, which avoids locks.

date 2021-07-09T10:42:35Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
message Simplify code supporting the new iwm(4) time quota firmware command.
There was no real need to use a separate function for this.

date 2021-07-09T10:45:17Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
message Reset sc_ucode_api flags before iwm(4) loads firmware.
Fixes firmware re-loading after an initial attempt to load firmware failed.

date 2021-07-09T10:46:56Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
message Ignore undocumented TLVs found in the iwm(4) 9000-43 firmware image.

date 2021-07-09T11:04:05Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
message Clear the "persistence bit" on iwm(4) 9k devices during hardware init.

According to iwlwifi commit messages this fixes an edge case where
9k family devices fail to resume after system suspend.
See Linux commit 8954e1eb2270fa2effffd031b4839253952c76f2

date 2021-07-09T11:11:36Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
message Make iwm(4) use only antenna B for single-antenna Tx on 9k devices.

This matches what Linux and FreeBSD do.
According to Linux commit logs using antenna A for single-antenna Tx
on 9k devices is "wrong" (with no further explanation given).
I suspect it only matters if Bluetooth is active, since antenna A has
obviously been working for us. But who knows...

date 2021-07-09T11:21:31Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
message Fix iwm(4) PHY context updates for newer firmware versions.

Firmware which advertises the BINDING_CDB_SUPPORT capability
needs a remove+add dance when the channel band has changed.

See Linux commit 730a18912bcbde0b94ae7f1b554a9908b3424a22
and Linux commit 91109f42d0ad0c0c282d1fa1257a1548977aa895

date 2021-07-09T11:24:55Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
src/sys/dev/pci/if_iwmreg.h log diff annotate
message Make iwm(4) set various scan command flags just like how iwlwifi sets them.
Discrepancies found while investigating an issue related to active scanning.

date 2021-07-09T11:29:08Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
message Do not ask iwm(4) firmware to send probe requests on passive channels.

This seems to fix a problem where newer 9k firmware versions become
unresponsive after association and eventually raise a fatal error.

date 2021-07-09T11:31:05Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
message Fix errors in the probe request template we provide to iwm(4) firmware.

The SSID should not be inserted into the template itself. The template
just needs an empty SSID information element. Firmware fills in the rest.

Fix the length specification of 2GHz band-specific data in the template.

date 2021-07-09T11:33:00Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
message remove unused lines of code from iwm(4) which were specific to iwx(4) devices

date 2021-07-09T11:36:14Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
message Print new iwm(4) firmware version numbers like Linux iwlwifi does it.

Starting with major version 35 the Linux driver prints the minor version
number in hexadecimal.

date 2021-07-09T11:41:20Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
message Switch iwm(4) to new firmware images available in iwm-firmware-20210512.

This updates firmware for 3165, 3168, 7265, 8260, 8265, 9260, 9560 devices.
Other devices did not receive firmware updates from Intel.
New firmware images should contain revelant fixes for fragattacks:
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00473.html

Running fw_update(1) may be required before rebooting into a new kernel.
sysupgrade(8) will take care of this.

Blocking issues reported during the previous attempt at using these firmware
images have been addressed.

When reporting issues, please enable 'ifconfig iwm0 debug', reproduce the
error once more, and include the full dmesg in your bug report.

date 2021-07-09T15:29:55Z
author bluhm
files src/sys/crypto/cryptosoft.c log diff annotate
src/sys/crypto/cryptosoft.h log diff annotate
message Use SLIST macro for cryptosoft sessions instead of hand rolled list.
OK mpi@ tobhe@

date 2021-07-09T20:19:46Z
author patrick
files src/sys/arch/arm64/stand/efiboot/conf.c log diff annotate
src/sys/arch/arm64/stand/efiboot/efiboot.c log diff annotate
message Parse /soc/dma-ranges to populate the openbsd,dma-constraint property.
On the MNT Reform, which uses a i.MX8MQ with 4 GB of memory, this makes
sure that we don't allocate DMA buffers above the 32-bit boundary. As
it turns out the i.MX8MQ's I/O devices are limited to 32-bit addresses.
The i.MX8MP seems to be better in that regard, though at least the USB
controller is still limited. That's a bit harder to fix in a dynamic
fashion, but we'll take care of that as soon as someone shows up with
an i.MX8MP with that much memory.

ok kettenis@

date 2021-07-09T20:43:28Z
author mvs
files src/sys/crypto/cryptodev.h log diff annotate
message Remove unused `cc_koperations' and `cc_queued' members from 'cryptocap'
struct.

ok bluhm@

date 2021-07-09T20:59:17Z
author jasper
files src/sys/ddb/db_sym.c log diff annotate
message fix scentence in db_printsym comment

date 2021-07-09T20:59:51Z
author jasper
files src/sys/arch/arm64/arm64/db_trace.c log diff annotate
src/sys/arch/riscv64/riscv64/db_trace.c log diff annotate
message use vaddr_t as type for frames as is commonly used elsewhere too

ok kettenis@