created | 2021-11-27T21:09:59Z |
---|---|
begin | 2021-11-23T00:00:00Z |
end | 2021-11-24T00:00:00Z |
path | src/sys |
commits | 4 |
date | 2021-11-23T00:17:59Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/ic/tea5757.c | log | diff | annotate |
src/sys/dev/pci/fmsradio.c | log | diff | annotate | |
message |
avoid clang -Wsometimes-uninitialized warnings in fms(4) feedback and ok millert@ |
date | 2021-11-23T01:03:35Z | |||
---|---|---|---|---|
author | deraadt | |||
files | src/sys/arch/arm64/arm64/cpu.c | log | diff | annotate |
message | limit a variable to the scope inside #ifdef where it is used |
date | 2021-11-23T01:44:44Z | |||
---|---|---|---|---|
author | kevlo | |||
files | src/sys/dev/pci/if_rge.c | log | diff | annotate |
message |
Fix mbuf leaks after reception error in rge_rxeof(). Being that rge(4) is derived from re(4) it looks like it has the same issues as fixed in re(4) rev 1.211. From Brad ok gnezdo@ |
date | 2021-11-23T19:13:45Z | |||
---|---|---|---|---|
author | kn | |||
files | src/sys/net/if_pppoe.c | log | diff | annotate |
message |
Use system uptime not UTC time to calculate PPPoE session duration Systems without RTC are likely to boot with wrong time, but pppoe(4) used microtime(9) anyway to remember when a new session began. (In)adequately, ifconfig(8) used gettimeofday(2) and calculated the difference between two absoloute dates to infer the PPPoE session duration. This goes off the rails if the wall clock jumps in between, e.g. due to NTP kicking in. Use getmicrouptime(9) and clock_gettime(2)/CLOCK_BOOTTIME instead to rely on the monotonically increasing system uptime instead to fix this. Reported and tested by Peter J. Philipp <pjp AT delphinusdns DOT org> on some octeon box without RTC. I've seen this on a Edgerouter 4 as well (2m uptime, 19d session). OK claudio |