All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: will@kernel.org, ryabinin.a.a@gmail.com, andreyknvl@gmail.com,
	dvyukov@google.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	elver@google.com, akpm@linux-foundation.org,
	gregkh@linuxfoundation.org, kasan-dev@googlegroups.com
Subject: Re: [PATCH v4 1/3] vmalloc: Choose a better start address in vm_area_register_early()
Date: Tue, 12 Oct 2021 19:21:20 +0100	[thread overview]
Message-ID: <YWXSIOm0u58vBfJ6@arm.com> (raw)
In-Reply-To: <20210910053354.26721-2-wangkefeng.wang@huawei.com>

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@huawei.com>

Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: will@kernel.org, ryabinin.a.a@gmail.com, andreyknvl@gmail.com,
	dvyukov@google.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	elver@google.com, akpm@linux-foundation.org,
	gregkh@linuxfoundation.org, kasan-dev@googlegroups.com
Subject: Re: [PATCH v4 1/3] vmalloc: Choose a better start address in vm_area_register_early()
Date: Tue, 12 Oct 2021 19:21:20 +0100	[thread overview]
Message-ID: <YWXSIOm0u58vBfJ6@arm.com> (raw)
In-Reply-To: <20210910053354.26721-2-wangkefeng.wang@huawei.com>

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@huawei.com>

Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>


  reply	other threads:[~2021-10-12 18:23 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10  5:33 [PATCH v4 0/3] arm64: support page mapping percpu first chunk allocator Kefeng Wang
2021-09-10  5:33 ` Kefeng Wang
2021-09-10  5:33 ` [PATCH v4 1/3] vmalloc: Choose a better start address in vm_area_register_early() Kefeng Wang
2021-09-10  5:33   ` Kefeng Wang
2021-10-12 18:21   ` Catalin Marinas [this message]
2021-10-12 18:21     ` Catalin Marinas
2021-09-10  5:33 ` [PATCH v4 2/3] arm64: Support page mapping percpu first chunk allocator Kefeng Wang
2021-09-10  5:33   ` Kefeng Wang
2021-09-17  6:24   ` Greg KH
2021-09-17  6:24     ` Greg KH
2021-09-17  6:55     ` Kefeng Wang
2021-09-17  6:55       ` Kefeng Wang
2021-09-17  7:04       ` Greg KH
2021-09-17  7:04         ` Greg KH
2021-09-17  7:24         ` Kefeng Wang
2021-09-17  7:24           ` Kefeng Wang
2021-09-10  5:33 ` [PATCH v4 3/3] kasan: arm64: Fix pcpu_page_first_chunk crash with KASAN_VMALLOC Kefeng Wang
2021-09-10  5:33   ` Kefeng Wang
2021-10-12 18:17   ` Catalin Marinas
2021-10-12 18:17     ` Catalin Marinas
2021-10-13  1:09     ` Kefeng Wang
2021-10-13  1:09       ` Kefeng Wang
2021-09-15  8:33 ` [PATCH v4 0/3] arm64: support page mapping percpu first chunk allocator Kefeng Wang
2021-09-15  8:33   ` Kefeng Wang
2021-09-16 15:41   ` Greg KH
2021-09-16 15:41     ` Greg KH
2021-09-17  1:11     ` Kefeng Wang
2021-09-17  6:24       ` Greg KH
2021-09-17  6:24         ` Greg KH
2021-09-28  7:48 ` Kefeng Wang
2021-09-28  7:48   ` Kefeng Wang
2021-10-08 13:33   ` Kefeng Wang
2021-10-08 13:33     ` Kefeng Wang
2021-10-10 21:36 ` Andrew Morton
2021-10-10 21:36   ` Andrew Morton
2021-10-11  1:09   ` Kefeng Wang
2021-10-11  1:09     ` Kefeng Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YWXSIOm0u58vBfJ6@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ryabinin.a.a@gmail.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.