linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Abbott Liu <liuwenliang@huawei.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Russell King <linux@armlinux.org.uk>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Andrey Ryabinin <aryabinin@virtuozzo.com>
Subject: Re: [PATCH 0/5 v2] KASan for ARM
Date: Mon, 1 Jun 2020 09:51:24 -0700	[thread overview]
Message-ID: <06784226-a1db-875f-1165-30579421bb8a@gmail.com> (raw)
In-Reply-To: <CAMj1kXGNSogYOBxZfoTq2uMtY-piZ3PePFVCs3-R5nBEvnx-Rg@mail.gmail.com>



On 6/1/2020 9:40 AM, Ard Biesheuvel wrote:
> On Mon, 1 Jun 2020 at 18:37, Florian Fainelli <f.fainelli@gmail.com> wrote:
>>
>>
>>
>> On 6/1/2020 1:55 AM, Linus Walleij wrote:
>>> On Mon, Jun 1, 2020 at 6:00 AM Florian Fainelli <f.fainelli@gmail.com> wrote:
>>>
>>>> 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?
>>>
>>> Oh I fixed most issues in the v9 patch set, we ironed out the actual problem
>>> with ARMv4 and ARMv5 with some help from Ard, Catalin and then Russell
>>> suggested how to also improve the way we get taskinfo from sp in the
>>> assembly.
>>>
>>>> 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.
>>>
>>> Did you try to use the v9 patch set on top of v5.7:
>>> https://lore.kernel.org/linux-arm-kernel/20200515114028.135674-1-linus.walleij@linaro.org/
>>>
>>> I need to rebase this on v5.8-rc1 once it is out but it is working on all my
>>> targets now, there is also this git branch:
>>> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-integrator.git/log/?h=kasan
>>
>> This branch got me a bit further, but still failed to fully initialize
>> (see attached kasan.log), on another platform with a slightly different
>> memory map, I ended up getting a different error (kasan2.log).
> 
> How can you be sure kasan2.log did not detect an actual bug?

I should have been clearer, my email was just sent out unfiltered to
report the status on Linus' branch, kasan2.log may be showing up a
genuine bug indeed.
-- 
Florian

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

  reply	other threads:[~2020-06-01 16:51 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 ` [PATCH 0/5 v2] " Florian Fainelli
2020-06-01  8:55   ` Linus Walleij
2020-06-01 16:36     ` Florian Fainelli
2020-06-01 16:40       ` Ard Biesheuvel
2020-06-01 16:51         ` Florian Fainelli [this message]
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=06784226-a1db-875f-1165-30579421bb8a@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;
as well as URLs for NNTP newsgroup(s).