| created | 2020-12-20T00:36:59Z |
|---|---|
| begin | 2020-12-16T00:00:00Z |
| end | 2020-12-17T00:00:00Z |
| path | src/sys |
| commits | 6 |
| date | 2020-12-16T15:06:11Z | |||
|---|---|---|---|---|
| author | visa | |||
| files | src/sys/kern/kern_event.c | log | diff | annotate |
| message |
Link kqpoll instances to fd_kqlist. This lets the system remove kqpoll-related event registrations when a file descriptor is closed. OK mpi@ |
|||
| date | 2020-12-16T15:07:30Z | |||
|---|---|---|---|---|
| author | visa | |||
| files | src/sys/kern/kern_event.c | log | diff | annotate |
| message |
Remove kqueue_free() and use KQRELE() in kqpoll_exit(). Because kqpoll instances are now linked to the file descriptor table, the freeing of kqpoll and ordinary kqueues is similar. Suggested by mpi@ |
|||
| date | 2020-12-16T18:00:44Z | |||
|---|---|---|---|---|
| author | kn | |||
| files | src/sys/net/pf_ioctl.c | log | diff | annotate |
| message |
Reject rules with invalid port ranges Ranges where the left boundary is bigger than the right one are always bogus as they work like `port any' (`port 34<>12' means "all ports") or in way that inverts the rule's action (`pass ... port 34:12' means "pass no port at all"). Add checks for all ranges and invalidate those that yield no or all ports. For this to work on redirections, make pfctl(8) pass the range's type, otherwise boundary including ranges are not detected as such; that is to say, `struct pf_pool's `port_op' member was unused in the kernel so far. `rdr-to' rules with invalid ranges could panic the kernel when hit. Reported-by: [email protected] OK sashan |
|||
| date | 2020-12-16T18:16:34Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/dev/softraid.c | log | diff | annotate |
| src/sys/dev/softraid_raid5.c | log | diff | annotate | |
| message |
softraid(4): more tsleep(9) -> tsleep_nsec(9) conversions These wait loops block for up to 1 tick per iteration. I think they will continue to work if we block for at least 1ms per iteration. My gut says that these could be rewritten not to spin and instead to await a wakeup(9) from the other thread, but I think that would involve making softraid(4) more MP-safe. |
|||
| date | 2020-12-16T19:28:59Z | |||
|---|---|---|---|---|
| author | tobhe | |||
| files | src/sys/netinet/ip_esp.c | log | diff | annotate |
| message |
Use ESP sequence number as IV for AES-CTR, AES-GCM and Chacha20. This eliminates the risk for IV reuse because of random collisions and increases performance a little. ok patrick@ markus@ |
|||
| date | 2020-12-16T21:11:35Z | |||
|---|---|---|---|---|
| author | bluhm | |||
| files | src/sys/arch/amd64/amd64/pmap.c | log | diff | annotate |
| message |
Do not clear useful bits in panic messages, always print full opte variable. Make PG_PVLIST panics consistent and print more values. OK mpi@ |
|||