On Fri, 18 Dec 2020 16:13:56 PST (-0800), Atish Patra wrote:

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: stable@vger.kernel.org

Reported-by: Bin Meng bin.meng@windriver.com Tested-by: Bin Meng bin.meng@windriver.com Acked-by: Mike Rapoport rppt@linux.ibm.com Signed-off-by: Atish Patra atish.patra@wdc.com

---

Changes from v1->v2:

1. Added stable-kernel in cc.
2. Added reported/tested by tag.

---

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

diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 13ba533f462b..bf5379135e39 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -176,7 +176,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);

Thanks, this is on fixes.