From: "Mike Rapoport (IBM)" <rppt@xxxxxxxxxx> LoongArch defines insane ranges for ARCH_FORCE_MAX_ORDER allowing MAX_ORDER up to 63, which implies maximal contiguous allocation size of 2^63 pages. Drop bogus definitions of ranges for ARCH_FORCE_MAX_ORDER and leave it a simple integer with sensible defaults. Users that *really* need to change the value of ARCH_FORCE_MAX_ORDER will be able to do so but they won't be mislead by the bogus ranges. Signed-off-by: Mike Rapoport (IBM) <rppt@xxxxxxxxxx> --- This applies to akpm/mm-unstable tree arch/loongarch/Kconfig | 3 --- 1 file changed, 3 deletions(-) diff --git a/arch/loongarch/Kconfig b/arch/loongarch/Kconfig index 272a3a12c98d..e1e3a3828962 100644 --- a/arch/loongarch/Kconfig +++ b/arch/loongarch/Kconfig @@ -420,11 +420,8 @@ config NODES_SHIFT config ARCH_FORCE_MAX_ORDER int "Maximum zone order" - range 13 63 if PAGE_SIZE_64KB default "13" if PAGE_SIZE_64KB - range 11 63 if PAGE_SIZE_16KB default "11" if PAGE_SIZE_16KB - range 10 63 default "10" help The kernel memory allocator divides physically contiguous memory -- 2.35.1
