created | 2020-08-09T08:17:23Z |
---|---|
begin | 2020-08-06T00:00:00Z |
end | 2020-08-07T00:00:00Z |
path | src/sys |
commits | 4 |
date | 2020-08-06T12:00:46Z | |||
---|---|---|---|---|
author | mvs | |||
files | src/sys/net/netisr.h | log | diff | annotate |
message |
Remove defines for `netisr' bits which are not used anymore. ok mpi@ |
date | 2020-08-06T14:06:12Z | |||
---|---|---|---|---|
author | mglocker | |||
files | src/sys/dev/usb/ehci.c | log | diff | annotate |
message |
Remove duplicate comment. ok mpi@ |
date | 2020-08-06T17:54:08Z | |||
---|---|---|---|---|
author | cheloha | |||
files | src/sys/kern/kern_timeout.c | log | diff | annotate |
message |
timeout(9): fix miscellaneous remote kcov(4) bugs Commit v1.77 introduced remote kcov support for timeouts. We need to tweak a few things to make our support more correct: - Set to_process for barrier timeouts to the calling thread's parent process. Currently it is uninitialized, so during timeout_run() we are passing stack garbage to kcov_remote_enter(9). - Set to_process to NULL during timeout_set_flags(9). If in the future we forget to properly initialize to_process before reaching timeout_run(), we'll pass NULL to kcov_remote_enter(9). anton@ says this is harmless. I assume it is also preferable to passing stack garbage. - Save a copy of to_process on the stack in timeout_run() before calling to_func to ensure that we pass the same process pointer to kcov_remote_leave(9) upon return. The timeout may be freely modified from to_func, so to_process may have changed when we return. Tested by anton@. ok anton@ |
date | 2020-08-06T19:47:44Z | |||
---|---|---|---|---|
author | bluhm | |||
files | src/sys/net/if_bridge.c | log | diff | annotate |
message |
Allow pf(4) to divert packets from bridge(4) to local socket. joint work markus@ patrick@ bluhm@ |