created | 2023-05-21T00:56:35Z |
---|---|
begin | 2023-04-04T00:00:00Z |
end | 2023-04-05T00:00:00Z |
path | src/sys |
commits | 4 |
date | 2023-04-04T00:38:37Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/conf/files | log | diff | annotate |
message | Synopsis Designware -> Synopsys DesignWare |
date | 2023-04-04T00:38:38Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/fdt/files.fdt | log | diff | annotate |
message | Synopsis Designware -> Synopsys DesignWare |
date | 2023-04-04T10:12:03Z | |||
---|---|---|---|---|
author | bluhm | |||
files | src/sys/netinet/ip_divert.c | log | diff | annotate |
src/sys/netinet6/ip6_divert.c | log | diff | annotate | |
message |
When sending IP packets to userland with divert-packet rules, the checksum may be wrong. Locally generated packets diverted by pf out rules may have no checksum due to to hardware offloading. Calculate the checksum in that case. OK mvs@ sashan@ |
date | 2023-04-04T21:49:10Z | |||
---|---|---|---|---|
author | cheloha | |||
files | src/sys/kern/kern_clockintr.c | log | diff | annotate |
message |
clockintr: add clockintr_cancel_locked() Move the CLST_PENDING check and TAILQ_REMOVE() in clockintr_schedule_locked() into a dedicated function, clockintr_cancel_locked(). clockintr_schedule_locked() no longer implicitly cancels a pending clockintr: it is the caller's responsibility to check for CLST_PENDING and cancel any pending expiration before calling clockintr_schedule_locked(). We can skip the CLST_PENDING check during the dispatch loop because we know for certain the clockintr in question is pending. This is more verbose but I think it is less surprising. Both functions do one thing. |