diff options
| author | glider@google.com <glider@google.com> | 2020-03-12 16:59:20 +0100 |
|---|---|---|
| committer | Catalin Marinas <catalin.marinas@arm.com> | 2020-03-17 18:36:57 +0000 |
| commit | c17a290f7e7e59d24b4507736b7b40b0eb5f8f1f (patch) | |
| tree | f140da9800e59eaca827dfd79efba4c1dc65b712 /arch/arm64/mm/proc.S | |
| parent | d22b115cbfbb7e4a938f9eb6ea77da9ecac3df5a (diff) | |
| download | linux-c17a290f7e7e59d24b4507736b7b40b0eb5f8f1f.tar.gz linux-c17a290f7e7e59d24b4507736b7b40b0eb5f8f1f.tar.bz2 linux-c17a290f7e7e59d24b4507736b7b40b0eb5f8f1f.zip | |
arm64: define __alloc_zeroed_user_highpage
When running the kernel with init_on_alloc=1, calling the default
implementation of __alloc_zeroed_user_highpage() from include/linux/highmem.h
leads to double-initialization of the allocated page (first by the page
allocator, then by clear_user_page().
Calling alloc_page_vma() with __GFP_ZERO, similarly to e.g. x86, seems
to be enough to ensure the user page is zeroed only once.
Signed-off-by: Alexander Potapenko <glider@google.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'arch/arm64/mm/proc.S')
0 files changed, 0 insertions, 0 deletions