[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210204124914.GC20468@willie-the-truck>
Date: Thu, 4 Feb 2021 12:49:14 +0000
From: Will Deacon <will@...nel.org>
To: Lecopzer Chen <lecopzer@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
kasan-dev@...glegroups.com, linux-arm-kernel@...ts.infradead.org,
dan.j.williams@...el.com, aryabinin@...tuozzo.com,
glider@...gle.com, dvyukov@...gle.com, akpm@...ux-foundation.org,
linux-mediatek@...ts.infradead.org, yj.chiang@...iatek.com,
catalin.marinas@....com, ardb@...nel.org, andreyknvl@...gle.com,
broonie@...nel.org, linux@...ck-us.net, rppt@...nel.org,
tyhicks@...ux.microsoft.com, robin.murphy@....com,
vincenzo.frascino@....com, gustavoars@...nel.org,
Lecopzer Chen <lecopzer.chen@...iatek.com>
Subject: Re: [PATCH v2 0/4] arm64: kasan: support CONFIG_KASAN_VMALLOC
On Sat, Jan 09, 2021 at 06:32:48PM +0800, Lecopzer Chen wrote:
> Linux supports KAsan for VMALLOC since commit 3c5c3cfb9ef4da9
> ("kasan: support backing vmalloc space with real shadow memory")
>
> Acroding to how x86 ported it [1], they early allocated p4d and pgd,
> but in arm64 I just simulate how KAsan supports MODULES_VADDR in arm64
> by not to populate the vmalloc area except for kimg address.
The one thing I've failed to grok from your series is how you deal with
vmalloc allocations where the shadow overlaps with the shadow which has
already been allocated for the kernel image. Please can you explain?
Thanks,
Will
Powered by blists - more mailing lists