| created | 2020-08-09T08:20:21Z |
|---|---|
| begin | 2020-08-07T00:00:00Z |
| end | 2020-08-08T00:00:00Z |
| path | src/sys |
| commits | 5 |
| date | 2020-08-07T00:45:25Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/kern/kern_timeout.c | log | diff | annotate |
| src/sys/sys/timeout.h | log | diff | annotate | |
| message |
timeout(9): remove unused interfaces: timeout_add_ts(9), timeout_add_bt(9) These two interfaces have been entirely unused since introduction. Remove them and thin the "timeout" namespace a bit. Discussed with mpi@ and ratchov@ almost a year ago, though I blocked the change at that time. Also discussed with visa@. ok visa@, mpi@ |
|||
| date | 2020-08-07T13:53:58Z | |||
|---|---|---|---|---|
| author | kevlo | |||
| files | src/sys/dev/pci/if_rge.c | log | diff | annotate |
| message |
- Do better work in ifmedia_upd - Eliminate the redundant bits of code for MTU handling; From Brad |
|||
| date | 2020-08-07T14:35:38Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/kern/uipc_socket.c | log | diff | annotate |
| message |
sosplice(9): fully validate idle timeout The socket splice idle timeout is a timeval, so we need to check that tv_usec is both non-negative and less than one million. Otherwise it isn't in canonical form. We can check for this with timerisvalid(3). benno@ says this shouldn't break anything in base. ok benno@, bluhm@ |
|||
| date | 2020-08-07T18:09:16Z | |||
|---|---|---|---|---|
| author | florian | |||
| files | src/sys/netinet6/in6.c | log | diff | annotate |
| message |
The IPv6 source address selection rewrite had one (known) difference to the previous behavior: In case of a tie the new implementation would keep the current best address while the old implementation replaced the best address. Since IPv6 addresses are stored in a TAILQ this meant that the rewrite would use the "oldest" address while the previous behavior was to use the "newest". RFC 6724 section 5 has no opinion which one is better and leaves the tie break up to implementers. naddy found out the hard way that this breaks his IPv6 connectivity in case of flash renumbering events when the link on his cpe flaps and a new prefix is used since we would always pick an old address. While we could pick the newest address in a tie break this feels too much like an implementation detail, a solution much more in the spirit of IPv6 is to pick the address with the highest preferred lifetime (or valid lifetime in case of another tie). very patient testing naddy@ |
|||
| date | 2020-08-07T20:12:15Z | |||
|---|---|---|---|---|
| author | tobhe | |||
| files | src/sys/net/pfkeyv2.c | log | diff | annotate |
| src/sys/net/pfkeyv2.h | log | diff | annotate | |
| message |
pfkey_get may allocate more memory than is needed to hold the SA information. Make sure to only copy out actually used memory. ok patrick@ |
|||