created | 2018-11-30T04:55:09Z |
---|---|
begin | 2018-09-18T00:00:00Z |
end | 2018-09-19T00:00:00Z |
path | src/sys |
commits | 6 |
date | 2018-09-18T06:36:18Z | |||
---|---|---|---|---|
author | mestre | |||
files | src/sys/net80211/ieee80211_node.c | log | diff | annotate |
message |
fix memory leak in ieee80211_end_scan() OK phessler@ jsg@ |
date | 2018-09-18T07:21:49Z | |||
---|---|---|---|---|
author | jmatthew | |||
files | src/sys/dev/pci/if_bnxt.c | log | diff | annotate |
message | cast HWRM_NA_SIGNATURE when shortening it to keep gcc happy, prodded by jsg@ |
date | 2018-09-18T13:45:09Z | |||
---|---|---|---|---|
author | deraadt | |||
files | src/sys/arch/arm64/conf/RAMDISK | log | diff | annotate |
message | grow arm64 ramdisk |
date | 2018-09-18T16:02:08Z | |||
---|---|---|---|---|
author | mlarkin | |||
files | src/sys/arch/amd64/amd64/vmm_support.S | log | diff | annotate |
message |
vmm(4): Reset host LDTR on exit for SVM For SVM machines, the LDT content remains set to that of the guest VM on exit (as compared to Intel/VMX which resets the LDTR to 0). This fix ensures the LDT is reset to 0 on SVM exits. Leaving the LDT set to the guest's choice could allow a malicious process to escalate its privileges with the help of a malicious VM that they also are able to run on the machine. This was reported by Maxime Villard; thanks! |
date | 2018-09-18T18:36:27Z | |||
---|---|---|---|---|
author | anton | |||
files | src/sys/ddb/db_command.c | log | diff | annotate |
message | whitespace fix; no binary change |
date | 2018-09-18T20:47:11Z | |||
---|---|---|---|---|
author | bluhm | |||
files | src/sys/kern/kern_tc.c | log | diff | annotate |
message |
Updating time counters without memory barriers is wrong. Put membar_producer() into tc_windup() and membar_consumer() into the uptime functions. They order the visibility of the time and generation number updates. This is a combination of what NetBSD and FreeBSD do. OK kettenis@ |