From: Florian Fainelli <f.fainelli@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Abbott Liu <liuwenliang@huawei.com>,
Russell King <linux@armlinux.org.uk>,
Ard Biesheuvel <ardb@kernel.org>,
Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5 v2] KASan for ARM
Date: Sun, 31 May 2020 21:00:09 -0700 [thread overview]
Message-ID: <107be5e0-3acd-1bf5-d1dd-e27f796e87d9@gmail.com> (raw)
In-Reply-To: <20200412002407.396790-1-linus.walleij@linaro.org>
Hi Linus,
On 4/11/2020 5:24 PM, Linus Walleij wrote:
> I am trying to pick up this series.
>
> I rebased it on what is soon v5.7-rc1 and fixed some bug
> or two (see individual ChangeLog on the patches).
>
> The main thing I need to fix here is the usage of TTBR0
> in patch 4. This isn't working for machines without
> TTBR0 obviously. I need help with the right approach
> here.
>
> I want to support all ARM CPUs that we support with the
> kernel and it is not far off: I tried it in Faraday's
> FA526 and it mostly works until we reach userspace
> and my guess is that that is because of the TTBR0
> shortcut it is taking.
>
> What is interesting is that if I compile in the KASan
> test module into the kernel, it performs most of the
> tests correctly even on this old platform, so we only
> have a few things to fix.
Since this patch series has had many people trying to push it forward,
how about we try to get it merged as-is (minus bugs, see below) with the
caveat that TTRB0-less CPUs are not going to be supported for now and
later on, this gets lifted if we find a champion who can get that working?
I tested this on an ARMv8 system (Brahma-B53 CPU) and an ARMv7-A system
(Brahma-B15 CPU) with and without ARM_LPAE enabled and neither were able
to boot unless KASAN was turned off (outline instrumentation), I don't
even get to the point where earlyprintk is giving me anything which is
odd. Have not looked at the differences between this version and the one
I had sent before and have not hooked a debugger to find out where we
are hung.
If you have a Raspberry Pi 4 you could use it as a test system for ARM_LPAE.
Thanks!
--
Florian
_______________________________________________
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:[~2020-06-01 4:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 0:24 [PATCH 0/5 v2] KASan for ARM Linus Walleij
2020-04-12 0:24 ` [PATCH 1/5 v2] ARM: Disable KASan instrumentation for some code Linus Walleij
2020-04-12 0:24 ` [PATCH 2/5 v2] ARM: Replace memory functions for KASan Linus Walleij
2020-04-12 0:24 ` [PATCH 3/5 v2] ARM: Define the virtual space of KASan's shadow region Linus Walleij
2020-04-12 0:24 ` [PATCH 4/5 v2] ARM: Initialize the mapping of KASan shadow memory Linus Walleij
2020-04-12 0:24 ` [PATCH 5/5 v2] ARM: Enable KASan for ARM Linus Walleij
2020-06-01 4:00 ` Florian Fainelli [this message]
2020-06-01 8:55 ` [PATCH 0/5 v2] " Linus Walleij
2020-06-01 16:36 ` Florian Fainelli
2020-06-01 16:40 ` Ard Biesheuvel
2020-06-01 16:51 ` Florian Fainelli
2020-06-03 8:45 ` Linus Walleij
2020-06-04 9:24 ` Linus Walleij
2020-06-04 11:26 ` Ard Biesheuvel
2020-06-04 12:10 ` Ard Biesheuvel
2020-06-04 17:01 ` Ard Biesheuvel
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=107be5e0-3acd-1bf5-d1dd-e27f796e87d9@gmail.com \
--to=f.fainelli@gmail.com \
--cc=ardb@kernel.org \
--cc=aryabinin@virtuozzo.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=liuwenliang@huawei.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