Commit 34f7c528 authored by Javier Martinez Canillas's avatar Javier Martinez Canillas Committed by Andrew Morton

mm/Kconfig: mention arm64 in DEFAULT_MMAP_MIN_ADDR symbol help text

Currently ppc64 and x86 are mentioned as architectures where a 65536 value
is reasonable but arm64 isn't listed and it is also a 64-bit architecture.

The help text says that for "arm" the value should be no higher than 32768
but it's only talking about 32-bit ARM.  Adding arm64 to the above list
can make this more clear and avoid confusing users who may think that the
32k limit would also apply to 64-bit ARM.

Link: https://lkml.kernel.org/r/20240619083047.114613-1-javierm@redhat.comSigned-off-by: default avatarJavier Martinez Canillas <javierm@redhat.com>
Cc: Brian Masney <bmasney@redhat.com>
Cc: Javier Martinez Canillas <javierm@redhat.com>
Cc: Maxime Ripard <mripard@kernel.org>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
parent 739820a6
...@@ -720,7 +720,7 @@ config DEFAULT_MMAP_MIN_ADDR ...@@ -720,7 +720,7 @@ config DEFAULT_MMAP_MIN_ADDR
from userspace allocation. Keeping a user from writing to low pages from userspace allocation. Keeping a user from writing to low pages
can help reduce the impact of kernel NULL pointer bugs. can help reduce the impact of kernel NULL pointer bugs.
For most ppc64 and x86 users with lots of address space For most arm64, ppc64 and x86 users with lots of address space
a value of 65536 is reasonable and should cause no problems. a value of 65536 is reasonable and should cause no problems.
On arm and other archs it should not be higher than 32768. On arm and other archs it should not be higher than 32768.
Programs which use vm86 functionality or have some need to map Programs which use vm86 functionality or have some need to map
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment