summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdlib
diff options
context:
space:
mode:
authorpatrick <patrick@openbsd.org>2017-03-24 13:04:16 +0000
committerpatrick <patrick@openbsd.org>2017-03-24 13:04:16 +0000
commit3efc265e49f3f8c020f2edab54ecd212fdf8353c (patch)
treeb331764d4b748fd21c62fb3b562e99fdcd1703a5 /lib/libc/stdlib
parentBackout mlarkin's previous commit while he is away: (diff)
downloadwireguard-openbsd-3efc265e49f3f8c020f2edab54ecd212fdf8353c.tar.xz
wireguard-openbsd-3efc265e49f3f8c020f2edab54ecd212fdf8353c.zip
Mainline u-boot on the ClearFog seems to insert an empty memory region
into the /memory node which we happily physload into UVM. This leads to a quickly panic(9)ing system when there is actual physical memory starting at zero due to how the physeg array is sorted when using the binary search strategy. To fix this, do not physload an empty memory region. ok jsg@ kettenis@
Diffstat (limited to 'lib/libc/stdlib')
0 files changed, 0 insertions, 0 deletions