From: Atish Patra <atish.pa...@wdc.com>

commit de043da0b9e71147ca610ed542d34858aadfc61c upstream.

memblock_enforce_memory_limit accepts the maximum memory size not the
maximum address that can be handled by kernel. Fix the function invocation
accordingly.

Fixes: 1bd14a66ee52 ("RISC-V: Remove any memblock representing unusable memory 
area")
Cc: sta...@vger.kernel.org
Reported-by: Bin Meng <bin.m...@windriver.com>
Tested-by: Bin Meng <bin.m...@windriver.com>
Acked-by: Mike Rapoport <r...@linux.ibm.com>
Signed-off-by: Atish Patra <atish.pa...@wdc.com>
Signed-off-by: Palmer Dabbelt <palmerdabb...@google.com>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>

---
 arch/riscv/mm/init.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/arch/riscv/mm/init.c
+++ b/arch/riscv/mm/init.c
@@ -174,7 +174,7 @@ void __init setup_bootmem(void)
         * Make sure that any memory beyond mem_start + (-PAGE_OFFSET) is 
removed
         * as it is unusable by kernel.
         */
-       memblock_enforce_memory_limit(mem_start - PAGE_OFFSET);
+       memblock_enforce_memory_limit(-PAGE_OFFSET);
 
        /* Reserve from the start of the kernel to the end of the kernel */
        memblock_reserve(vmlinux_start, vmlinux_end - vmlinux_start);


Reply via email to