| created | 2019-05-25T11:04:47Z |
|---|---|
| begin | 2019-05-22T00:00:00Z |
| end | 2019-05-23T00:00:00Z |
| path | src/sys |
| commits | 8 |
| date | 2019-05-22T15:23:01Z | |||
|---|---|---|---|---|
| author | patrick | |||
| files | src/sys/dev/ic/bwfm.c | log | diff | annotate |
| message |
If we are SCANning and we want another SCAN, we don't need to purge all nodes and set the link down, this already happened the first time we went to SCAN mode. This brings us in line with the net80211 stack and fixes an incomplete node list during ifconfig(8) scan. |
|||
| date | 2019-05-22T15:25:25Z | |||
|---|---|---|---|---|
| author | patrick | |||
| files | src/sys/dev/ic/bwfm.c | log | diff | annotate |
| message | Print the bwfm(4)'s ethernet address on attach. | |||
| date | 2019-05-22T15:40:48Z | |||
|---|---|---|---|---|
| author | kettenis | |||
| files | src/sys/arch/amd64/stand/efiboot/exec_i386.c | log | diff | annotate |
| message |
Allow loading of bigger ucode. This implementation uses the UEFI memory allocation service to allocate a block of memory below 16MB such that there is no risk of overwriting it when the bootloader moves the kernel in place. It removes the 128k limit that was previously there. Based on an earlier diff by patrick@ ok mlarkin@ |
|||
| date | 2019-05-22T16:11:21Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/arch/i386/i386/apm.c | log | diff | annotate |
| message |
i386/amd64 apm(4): Ignore APM_UPDATE_TIME events. The APM spec defines an APM_UPDATE_TIME event that is meant to cause the driver to rebase the system's wallclock against the RTC. The event itself is apparently caused by occasional blackout periods where interrupts cannot be delivered, which might cause the system to miss a tick. The problem is that on systems where these events are frequent this constantly erodes the system wallclock. The RTC is not the greatest clock in the world so these systems are always playing catch-up. ntpd(8) is a far better clock corrector than rebasing against the RTC, so it should be safe to simply ignore the event. We continue to record the event for userspace listeners, but we do not call inittodr(9) on receipt of the event. Linux has ignored the event since v2.6.21: https://github.com/torvalds/linux/commit/c1d370e167d66b10bca3b602d3740405469383de#diff-d85b9a44da8e5dfb2fb1bcbd304c2a6c Discovered by jcs@. Discussed a bit with jcs@, tedu@, deraadt@. Fix tested by jcs@. "I think we should ignore the event" deraadt@ |
|||
| date | 2019-05-22T18:45:07Z | |||
|---|---|---|---|---|
| author | claudio | |||
| files | src/sys/kern/kern_sysctl.c | log | diff | annotate |
| message |
Read and assign the integer value only once. With this sysctl_int() will do word loads and stores and so partial updates should no longer be observed. With this accessing global variables set by sysctl_int() should be mostly MP save. OK dlg@ mpi@ |
|||
| date | 2019-05-22T18:52:14Z | |||
|---|---|---|---|---|
| author | anton | |||
| files | src/sys/dev/wscons/wsevent.c | log | diff | annotate |
| src/sys/dev/wscons/wseventvar.h | log | diff | annotate | |
| src/sys/dev/wscons/wskbd.c | log | diff | annotate | |
| src/sys/dev/wscons/wsmouse.c | log | diff | annotate | |
| src/sys/dev/wscons/wsmux.c | log | diff | annotate | |
| message |
A wscons device may only be opened in read/write mode once. However, after checking for exclusive access, malloc() can sleep in wsevent_init() opening up for a potential race where more than one thread may be able open the device. Prevent this by checking if the race was won after calling malloc(). While here, switch to mallocarray as proposed by both cheloha@ and mpi@ ok mpi@ |
|||
| date | 2019-05-22T19:13:34Z | |||
|---|---|---|---|---|
| author | anton | |||
| files | src/sys/dev/wscons/wskbd.c | log | diff | annotate |
| src/sys/dev/wscons/wsmouse.c | log | diff | annotate | |
| src/sys/dev/wscons/wsmux.c | log | diff | annotate | |
| message |
Cleanup debug macros in wscons. Favor __func__ over spelling out the actual function name in order to reduce grep noise. Also, some of them where referring to the wrong function. |
|||
| date | 2019-05-22T19:59:37Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/kern/kern_tc.c | log | diff | annotate |
| src/sys/sys/timetc.h | log | diff | annotate | |
| message |
SLIST-ify the timecounter list. Call it "tc_list" instead of "timecounters", which is too similar to the variable "timecounter" for my taste. ok mpi@ visa@ |
|||