| created | 2024-07-04T00:36:15Z |
|---|---|
| begin | 2024-06-21T00:00:00Z |
| end | 2024-06-22T00:00:00Z |
| path | src/sys |
| commits | 2 |
| date | 2024-06-21T01:52:17Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/arch/arm64/arm64/cpu.c | log | diff | annotate |
| message | recognise Qualcomm Oryon; ok kettenis@ | |||
| date | 2024-06-21T12:51:29Z | |||
|---|---|---|---|---|
| author | sashan | |||
| files | src/sys/net/pf.c | log | diff | annotate |
| src/sys/net/pfvar_priv.h | log | diff | annotate | |
| message |
My earlier commit [1.1169 of pf.c (2023/01/05)] makes pf(4) to report wrong rule and anchor number when packet matches rule found and anchor depth 2 and more. The issue has been noticed and reported by Giannis Kapetanakis (billias _at_ edu.physics.uoc.gr), who also co-developed and tested the final fix presented in this commit. To fix the issue pf(4) must also remember the anchor where matching rule belongs while rules are traversed to find a match for given packet. The information on anchor is now kept in anchor stack frame.w OK sthen@ |
|||