by range_test. This fixes msync, mlock and munlock, which all return EINVAL
instead of ENOMEM if the address is not in the va space.
It should also fix the recent ATF failures.
- t0/t1 weren't being updated when both lo0/lo1 become invalid
- the global bit (G) needs to be preserved if the entry becomes invalid
The MIPSNN optimisation is disabled for now as it needs to be updated
appropriately
the contents of the sub-tree are all structures, and thus not displayed
via sysctl(8), the info is potentially useful to programs. (For example,
ccdconfig could use this to determine how many units are available.)
The sub-tree is already available when the module is included as built-in
module.
Summary of changes in tzdata2016f (2016-07-05 16:26:51 +0200):
* The Egyptian government changed its mind on short notice, and
Africa/Cairo will not introduce DST starting 2016-07-07 after all.
* Asia/Novosibirsk switches from +06 to +07 on 2016-07-24 at 02:00.
* Asia/Novokuznetsk and Asia/Novosibirsk now use numeric time zone
abbreviations instead of invented ones.
* Europe/Minsk's 1992-03-29 spring-forward transition was at 02:00 not 00:00.
Summary of changes in tzdata2016e (2016-06-14 08:46:16 -0700):
* Africa/Cairo observes DST in 2016 from July 7 to the end of October.
(change obsoleted by 2016f)
* Locations while uninhabited now use '-00', not 'zzz', as a
placeholder time zone abbreviation.
* Asia/Baku's 1992-09-27 transition from +04 (DST) to +04 (non-DST) was
at 03:00, not 23:00 the previous day.
* zic now outputs a dummy transition at time 2**31 - 1 in zones
whose POSIX-style TZ strings contain a '<'.
* Changes affecting documentation and commentary.
The GPIO lines on an ICH are usually connected to opaque platform-
defined functionality, and may be manipulated by the ACPI DSDT or other
mechanisms behind our backs. In one instance, it was found this
in combiation with gpio_resume() sabotaged repeated suspend/resume cycles.
GPIO functionality can be enabled by setting ichlpcib_gpio_disable to 0,
for instance with `gdb -write`.
zero is hugely flawed. It is easy to demonstrate that one can trick UVM
into chosing a NULL hint after the user_va0_disable check from uvm_map.
Such a bypass allows kernel NULL pointer dereferences to be exploitable on
architectures with a shared userland<->kernel VA, like amd64.
Fix this by increasing the limit of the vm space made available for
userland processes. This way, UVM will never chose a NULL hint, since it
would be outside of the vm space.
The user_va0_disable sysctl still controls this feature.
