| created | 2020-01-04T20:13:10Z |
|---|---|
| begin | 2020-01-03T00:00:00Z |
| end | 2020-01-04T00:00:00Z |
| path | src/sys |
| commits | 9 |
| date | 2020-01-03T00:51:55Z | |||
|---|---|---|---|---|
| author | dlg | |||
| files | src/sys/dev/pci/pcidevs | log | diff | annotate |
| message | add some more samsung nvme ids | |||
| date | 2020-01-03T00:52:47Z | |||
|---|---|---|---|---|
| author | dlg | |||
| files | src/sys/dev/pci/pcidevs.h | log | diff | annotate |
| src/sys/dev/pci/pcidevs_data.h | log | diff | annotate | |
| message | regen | |||
| date | 2020-01-03T01:16:12Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/kern/kern_timeout.c | log | diff | annotate |
| src/sys/sys/timeout.h | log | diff | annotate | |
| message |
timeout(9): Rename the TIMEOUT_NEEDPROCCTX flag to TIMEOUT_PROC. This makes it more likely to fit into 80 columns if used alongside the forthcoming timeout_set_flags() and TIMEOUT_INITIALIZER_FLAGS() interfaces. "makes sense to me" bluhm@, ok visa@ |
|||
| date | 2020-01-03T02:16:38Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/kern/kern_timeout.c | log | diff | annotate |
| src/sys/sys/timeout.h | log | diff | annotate | |
| message |
timeout(9): Add timeout_set_flags(9) and TIMEOUT_INITIALIZER_FLAGS(9) These allow the caller to initialize timeouts with arbitrary flags. We only have one flag at the moment, TIMEOUT_PROC, but experimenting with other flags is easier if these interfaces are available in-tree. With input from bluhm@, guenther@, and visa@. "makes sense to me" bluhm@, ok visa@ |
|||
| date | 2020-01-03T05:37:00Z | |||
|---|---|---|---|---|
| author | visa | |||
| files | src/sys/kern/kern_descrip.c | log | diff | annotate |
| src/sys/kern/kern_event.c | log | diff | annotate | |
| src/sys/sys/filedesc.h | log | diff | annotate | |
| message |
Fix a file descriptor close race in kqueue_register() After inserting a knote, check that the associated file descriptor still references the same file. Remove the knote if the descriptor has changed because otherwise the kqueue becomes inconsistent with the file descriptor table. There is an analogous race in fcntl(F_SETLK). It is already handled, but the code can be simplified by using the same check as in kqueue_register(). Fix inspired by DragonFly BSD OK mpi@, anton@ |
|||
| date | 2020-01-03T08:39:31Z | |||
|---|---|---|---|---|
| author | kn | |||
| files | src/sys/dev/pci/mpii.c | log | diff | annotate |
| message |
Fix RAID volume WWIDs for LSI controllers on sparc64 Some controllers generate 128 bit WWIDs for RAID volumes but only has a 64-bit field to report it to the host, so it only puts the vendor-specified part here (last half of ID string printed when sd* attaches matches sl->port_wwn in reverse). As such IDs are not IEEE NAA compliant, OpenBoot PROM -at least on SPARC- sets the highest nibble to three by convention to mark such volumes as RAID volumes so that the OS (Solaris) may identify it as such. This is the last missing piece to make booting off hardware RAID on sparc64 just work; autoconf(9) is now able to match the port WWN against the bootpath to eventually identify the volume as the root device. Feedback jmatthew deraadt OK jmatthew |
|||
| date | 2020-01-03T09:46:41Z | |||
|---|---|---|---|---|
| author | claudio | |||
| files | src/sys/kern/kern_sig.c | log | diff | annotate |
| src/sys/sys/signalvar.h | log | diff | annotate | |
| message |
Retire csignal() the last users were converted to use pgsigio(9) instead. OK visa@ anton@ |
|||
| date | 2020-01-03T15:18:02Z | |||
|---|---|---|---|---|
| author | anton | |||
| files | src/sys/kern/sys_pipe.c | log | diff | annotate |
| message |
Rename the pipe I/O lock routines for improved clarity. This is just a mere preparation for introducing a dedicated lock per pipe pair. ok mpi@ visa@ |
|||
| date | 2020-01-03T20:11:11Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/kern/kern_timeout.c | log | diff | annotate |
| message |
timeout(9): delay thread wakeup(9) decision to end of softclock() loop The process-context timeout(s) in question might be cancelled before we leave the loop, leading to a spurious wakeup(9). ok mpi@ |
|||