| created | 2022-11-26T11:46:39Z |
|---|---|
| begin | 2022-11-25T00:00:00Z |
| end | 2022-11-26T00:00:00Z |
| path | src/sys |
| commits | 6 |
| date | 2022-11-25T03:20:09Z | |||
|---|---|---|---|---|
| author | dlg | |||
| files | src/sys/dev/ic/nvme.c | log | diff | annotate |
| message |
nvme can do 64bit dma. ok jmatthew@ |
|||
| date | 2022-11-25T03:45:39Z | |||
|---|---|---|---|---|
| author | dlg | |||
| files | src/sys/net/pf.c | log | diff | annotate |
| message |
get rid of NET_LOCK in the pf purge work pf purge was moved to systqmp (to get it away from KERNEL_LOCK) which is also used as the backend for things like intr_barrier and sched_barrier. it is common for network cards to call intr_barrier while holding NET_LOCK, and if pf is trying to get the NET_LOCK in the purge tasks that are now running in systqmp, it's a deadlock. bluhm@ hit this exact issue. sashan@ has been working to get rid of the need for NET_LOCK in pf, so now we can remove the NET_LOCKs here rather than create a pf specific taskq to run these tasks in. ok sashan@ bluhm@ |
|||
| date | 2022-11-25T15:03:24Z | |||
|---|---|---|---|---|
| author | kn | |||
| files | src/sys/netinet6/nd6.c | log | diff | annotate |
| message | Revert hunk accidentially committed in r1.248 "Clarify/typofix comments" | |||
| date | 2022-11-25T18:03:53Z | |||
|---|---|---|---|---|
| author | kettenis | |||
| files | src/sys/net/pf.c | log | diff | annotate |
| message |
Revert previous commit. It was not properly tested and produces splassert warnings. Rushing to pile more stuff on top of it isn't the answer. This needs a rethink. ok deraadt@ |
|||
| date | 2022-11-25T20:27:53Z | |||
|---|---|---|---|---|
| author | bluhm | |||
| files | src/sys/net/pf.c | log | diff | annotate |
| src/sys/net/pf_ioctl.c | log | diff | annotate | |
| src/sys/net/pfvar.h | log | diff | annotate | |
| src/sys/net/pfvar_priv.h | log | diff | annotate | |
| message |
revert pf.c r1.1152 again: move pf_purge out from under the kernel lock Using systqmp for pf_purge creates a deadlock between pf_purge() and ixgbe_stop() and possibly other drivers. On systqmp pf(4) needs netlock which the interface ioctl(2) is holding. ix(4) waits in sched_barrier() which is also scheduled on the systqmp task queue. Removing the netlock from pf_purge() as a quick fix caused other problems. backout suggested by deraadt@ |
|||
| date | 2022-11-25T20:33:11Z | |||
|---|---|---|---|---|
| author | tobhe | |||
| files | src/sys/arch/arm64/dev/aplsmc.c | log | diff | annotate |
| message |
Disable screen backlight on Apple silicon laptops when lid is closed. ok kettenis@ |
|||