lkml.org 
[lkml]   [2020]   [Dec]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 5.10 594/717] RISC-V: Fix usage of memblock_enforce_memory_limit
    Date
    From: Atish Patra <atish.patra@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: 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>
    Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@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);

    \
     
     \ /
      Last update: 2020-12-28 15:43    [W:4.400 / U:0.004 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site