| created | 2023-05-13T20:57:47Z |
|---|---|
| begin | 2023-05-11T00:00:00Z |
| end | 2023-05-12T00:00:00Z |
| path | src/sys |
| commits | 3 |
| date | 2023-05-11T09:51:33Z | |||
|---|---|---|---|---|
| author | bluhm | |||
| files | src/sys/kern/kern_ktrace.c | log | diff | annotate |
| message |
mi_syscall() can add the KTRC_CODE_SYSCALL flag to the syscall code. In ktrsyscall() mask the code, otherwise kdump(1) does not show the correct mib of SYS_sysctl when called by syscall(2). OK guenther@ |
|||
| date | 2023-05-11T12:36:22Z | |||
|---|---|---|---|---|
| author | kn | |||
| files | src/sys/net/pf_ioctl.c | log | diff | annotate |
| message |
pools are always initialised, zap overcautious NULL check All pools are init'd after pfattach(), none is ever destroyed, so struct pf_pool_limit's .pp always points to valid pools. Drop a check for the impossible from twenty years ago. OK sashan dlg |
|||
| date | 2023-05-11T16:55:46Z | |||
|---|---|---|---|---|
| author | stsp | |||
| files | src/sys/dev/pci/if_iwx.c | log | diff | annotate |
| message |
Stop sending a PHY context update in iwx_run_stop() Fixes firmware error iwx0: 0x20101A28 | ADVANCED_SYSASSERT which would occur while tearing down the state of our association to the AP. The problem occurred when we were trying to reconfigure the PHY context in a way that is incompatible with the TLC configuration. Since we will always call iwx_deauth() next, which removes the AP station and related data such as TLC from firmware before updating the PHY context yet again we can simply skip the redundant PHY context update in iwx_run_stop() to prevent this firmware error. A reliable way to reproduce the problem is an attempt to connect to an 11ac access point on a 5GHz channel while the wrong WPA key is set which happened to me because mpi@ uses a French WPA passphrase. Problem confirmed fixed by me with this simple reproducer. Helpful hints provided by Johannes Berg at Linux/Intel, thanks! |
|||