| created | 2019-03-30T17:10:17Z |
|---|---|
| begin | 2019-03-26T00:00:00Z |
| end | 2019-03-27T00:00:00Z |
| path | src/sys |
| commits | 6 |
| date | 2019-03-26T04:24:22Z | |||
|---|---|---|---|---|
| author | visa | |||
| files | src/sys/kern/kern_sched.c | log | diff | annotate |
| message |
Make sure that each ci has its spc_deferred queue initialized. Otherwise, the system can crash in smr_call_impl() if SMT is enabled later. Crash reported by jcs@ |
|||
| date | 2019-03-26T13:41:40Z | |||
|---|---|---|---|---|
| author | beck | |||
| files | src/sys/kern/kern_unveil.c | log | diff | annotate |
| message |
Remove this assert, I can't do this here with UNVEIL_INSPECT added aggressively today. Hopefully post release a glorious flensing will remove UNVEIL_INSPECT anyway Reported-by: [email protected] |
|||
| date | 2019-03-26T16:02:54Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/kern/kern_time.c | log | diff | annotate |
| message |
adjtime(2): set EINVAL if delta overflows 64 bits of microseconds. No other (known) BSD-derived adjtime(2) implementation checks for overflow when converting delta into its final denomination of fractional seconds. This is peculiar, as the call originates in 4.3BSD. However, glibc, uclibc, and (to an extent) musl /do/ check the input and set EINVAL if it exceeds a certain bound, so we'll just use the errno that they use to be consistent with extant practice. Prompted by the comment kettenis@ left when we switched to storing the adjustment in an int64_t like ~5 years ago (kern_time.c,v 1.87). Positive feedback from deraadt@, manpage bits ok jmc@, no code complaints from otto@ or tedu@. |
|||
| date | 2019-03-26T16:43:56Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/kern/kern_time.c | log | diff | annotate |
| message |
Tweak previous: include |
|||
| date | 2019-03-26T19:32:46Z | |||
|---|---|---|---|---|
| author | mlarkin | |||
| files | src/sys/arch/amd64/include/cpufunc.h | log | diff | annotate |
| message |
vmm(4): On VMX, use sgdt/sidt to reset the GDT/IDT limits after exiting the guest VM. By default, VMX sets the limits to 0xFFFF on exit, which is larger than what we want and can lead to security issues. While here, reset the LDT as well. We don't use this in OpenBSD, and VMX loads a null LDT selector on exit anyway, but resetting it here prevents any future surprises. Pointed out by Maxime Villard from NetBSD - thanks! ok deraadt@ |
|||
| date | 2019-03-26T19:32:47Z | |||
|---|---|---|---|---|
| author | mlarkin | |||
| files | src/sys/arch/amd64/amd64/vmm.c | log | diff | annotate |
| message |
vmm(4): On VMX, use sgdt/sidt to reset the GDT/IDT limits after exiting the guest VM. By default, VMX sets the limits to 0xFFFF on exit, which is larger than what we want and can lead to security issues. While here, reset the LDT as well. We don't use this in OpenBSD, and VMX loads a null LDT selector on exit anyway, but resetting it here prevents any future surprises. Pointed out by Maxime Villard from NetBSD - thanks! ok deraadt@ |
|||