| created | 2024-12-22T00:01:52Z |
|---|---|
| begin | 2024-12-18T00:00:00Z |
| end | 2024-12-19T00:00:00Z |
| path | src/sys |
| commits | 3 |
| date | 2024-12-18T01:56:05Z | |||
|---|---|---|---|---|
| author | dlg | |||
| files | src/sys/net/if_aggr.c | log | diff | annotate |
| message |
let LLDP packets fall through to being handled on the port interfaces. 802.1ax says that LLDP packets sent to the multicast groups listed in 802.1ab (the lldp spec) should be treated as "control frames" so they can be processed by an lldp agent on physical interface. in our situation that means we shouldn't aggregate LLDP packets so they appear to enter the system on aggr(4) interfaces, we should let the physical port interfaces handle them. this will allow AF_FRAME sockets listening on aggr port interfaces receive lldp packets. jmatthew@ says it looks good. |
|||
| date | 2024-12-18T02:25:30Z | |||
|---|---|---|---|---|
| author | dlg | |||
| files | src/sys/net/if_pfsync.c | log | diff | annotate |
| message |
go back to r1.326, before i fiddled with packet generation and bpf. i've had a couple of reports of redundant firewalls misbehaving since these changes, so until i can figure out what's wrong i'm backing them out. reported by hrvoje popovski and mark patruck |
|||
| date | 2024-12-18T16:41:27Z | |||
|---|---|---|---|---|
| author | mpi | |||
| files | src/sys/uvm/uvm_aobj.c | log | diff | annotate |
| src/sys/uvm/uvm_fault.c | log | diff | annotate | |
| src/sys/uvm/uvm_vnode.c | log | diff | annotate | |
| message |
Do not busy pages that are resident & fetched with PGO_LOCKED. This is safe because the rwlock of the related object is never released until the handler is done with the pages. ok kettenis@, tb@ |
|||