[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YWXSIOm0u58vBfJ6@arm.com>
Date: Tue, 12 Oct 2021 19:21:20 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Kefeng Wang <wangkefeng.wang@...wei.com>
Cc: will@...nel.org, ryabinin.a.a@...il.com, andreyknvl@...il.com,
dvyukov@...gle.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, elver@...gle.com,
akpm@...ux-foundation.org, gregkh@...uxfoundation.org,
kasan-dev@...glegroups.com
Subject: Re: [PATCH v4 1/3] vmalloc: Choose a better start address in
vm_area_register_early()
On Fri, Sep 10, 2021 at 01:33:52PM +0800, Kefeng Wang wrote:
> There are some fixed locations in the vmalloc area be reserved
> in ARM(see iotable_init()) and ARM64(see map_kernel()), but for
> pcpu_page_first_chunk(), it calls vm_area_register_early() and
> choose VMALLOC_START as the start address of vmap area which
> could be conflicted with above address, then could trigger a
> BUG_ON in vm_area_add_early().
>
> Let's choose a suit start address by traversing the vmlist.
>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@...wei.com>
Reviewed-by: Catalin Marinas <catalin.marinas@....com>
Powered by blists - more mailing lists