summaryrefslogtreecommitdiffstats
path: root/scripts/Kbuild.include
diff options
context:
space:
mode:
authorAlexander Graf <agraf@suse.de>2018-11-05 00:30:46 +0100
committerAlexander Graf <agraf@suse.de>2018-12-02 21:59:37 +0100
commitc2e1ad70a75048d802bf5c3296a043761939dae6 (patch)
treea028f0210ed113a4ccbd305f695d565ccb5c8509 /scripts/Kbuild.include
parentafdc4fcc8931589f2fab75d8830ab9b43d2725c4 (diff)
efi_loader: Ensure memory allocations are page aligned
When the max_addr parameter of efi_find_free_memory() is within bounds of an existing map and fits the reservation, we just return that address as allocation value. That breaks however if max_addr is not page aligned. So ensure that it always comes to us page aligned, simplifying the allocation logic. Without this, I've seen breakage where we were allocating pages at -1U (32bit) which fits into a region that spans beyond 0x100000000. In that case, we would return 0xffffffff as a valid memory allocation, although we usually do guarantee they are all page aligned. Fix this by aligning the max address argument always. Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'scripts/Kbuild.include')
0 files changed, 0 insertions, 0 deletions