From: Linus Walleij <linus.walleij@linaro.org>
To: 李文杰 <liwenjie.liwenjie@bytedance.com>
Cc: linux-arm-kernel@lists.infradead.org,
Lecopzer Chen <lecopzer.chen@mediatek.com>
Subject: Re: kasan-for-arm32
Date: Thu, 10 Nov 2022 10:51:40 +0100 [thread overview]
Message-ID: <CACRpkdZ9zKvBkwRHi2n=m5F7bi+z-d12YKdbaAuicbsX_PSYmg@mail.gmail.com> (raw)
In-Reply-To: <CAO1F-4p04rkLu5O1v5V+mYhW+A-cQrbM9McBS5Tu4t=qrWO_pg@mail.gmail.com>
On Wed, Nov 9, 2022 at 12:14 PM 李文杰 <liwenjie.liwenjie@bytedance.com> wrote:
[Contex: porting kasan to kernel v5.4]
> 1. I know why my machine crash after porting the patch.
> 2. Because the kernel access the vmalloc region, which not shadowed.
> 3. Now I found at least two places where used vmalloc region:
> 1). arch/arm/mm/fault-armv.c ->check_writebuffer_bugs() -> vmap();
> 2). lib/genalloc.c -> chunk = vzalloc_node(nbytes, nid);
> 4. could I add the vmalloc to shadow memory region?
I think you need to backport at least the following patches from upstream:
823f606ab6b4 ARM: 9242/1: kasan: Only map modules if CONFIG_KASAN_VMALLOC=n
565cbaad83d8 ARM: 9202/1: kasan: support CONFIG_KASAN_VMALLOC
Both from Lecopzer Chen.
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-10 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 11:14 kasan-for-arm32 李文杰
2022-11-10 9:51 ` Linus Walleij [this message]
2022-11-10 16:17 ` [External] kasan-for-arm32 李文杰
2022-11-10 22:43 ` Florian Fainelli
2022-11-11 7:53 ` 李文杰
2022-11-28 7:06 ` 李文杰
2022-12-18 10:46 ` 李文杰
-- strict thread matches above, loose matches on Subject: below --
2023-01-29 3:41 kasan-for-arm32 李文杰
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='CACRpkdZ9zKvBkwRHi2n=m5F7bi+z-d12YKdbaAuicbsX_PSYmg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liwenjie.liwenjie@bytedance.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).