[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkda_hpTVxKftKBqRvBtC-KN8c9NWHFJDV10TN4JOR7CQCw@mail.gmail.com>
Date: Wed, 27 Apr 2022 15:01:48 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Lecopzer Chen <lecopzer.chen@...iatek.com>
Cc: linux@...linux.org.uk, andreyknvl@...il.com,
anshuman.khandual@....com, ardb@...nel.org, arnd@...db.de,
dvyukov@...gle.com, geert+renesas@...der.be, glider@...gle.com,
kasan-dev@...glegroups.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, lukas.bulwahn@...il.com,
mark.rutland@....com, masahiroy@...nel.org, matthias.bgg@...il.com,
rmk+kernel@...linux.org.uk, ryabinin.a.a@...il.com,
yj.chiang@...iatek.com
Subject: Re: [PATCH v5 0/2] arm: kasan: support CONFIG_KASAN_VMALLOC
On Wed, Apr 27, 2022 at 11:59 AM Lecopzer Chen
<lecopzer.chen@...iatek.com> wrote:
> Since the framework of KASAN_VMALLOC is well-developed,
> It's easy to support for ARM that simply not to map shadow of VMALLOC
> area on kasan_init.
>
> Since the virtual address of vmalloc for Arm is also between
> MODULE_VADDR and 0x100000000 (ZONE_HIGHMEM), which means the shadow
> address has already included between KASAN_SHADOW_START and
> KASAN_SHADOW_END.
> Thus we need to change nothing for memory map of Arm.
>
> This can fix ARM_MODULE_PLTS with KASan, support KASan for higmem
> and support CONFIG_VMAP_STACK with KASan.
Excellent Lecopzer,
can you put these patches into Russell's patch tracker so he can pick them?
https://www.armlinux.org.uk/developer/patches/
Yours,
Linus Walleij
Powered by blists - more mailing lists