linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Abbott Liu <liuwenliang@huawei.com>,
	Russell King <linux@armlinux.org.uk>,
	Andrey Ryabinin <aryabinin@virtuozzo.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/5 v8] KASan for Arm
Date: Thu, 7 May 2020 19:29:13 +0200	[thread overview]
Message-ID: <CAMj1kXGT1WhX=A2q3yH=rOpBcTvXv1-mCujrt_5AAaoATwh9Sw@mail.gmail.com> (raw)
In-Reply-To: <20200507124522.171323-1-linus.walleij@linaro.org>

On Thu, 7 May 2020 at 14:47, Linus Walleij <linus.walleij@linaro.org> wrote:
>
> It's time to repost this, now that I got it into better shape.
>
> Main changes:
> - Restore the series number to v8 following my previous
>   "v1" which was actually v7, following Florians versions.
>   What was I thinking. :(
> - Doesn't crash randomly in QEMU etc. This was because
>   mmu.c was instrumented, and when we were lucky this did
>   not poke around in memory that crashed us.
> - Handle the undefined symbols better (like suggested by
>   Ard)
> - Fix up documentation.
> - Better patch split in logical chunks.
>
> Remaining issues:
> - Does it work for you?
> - Crash on ARMv5/v5 in v4wbi_flush_user_tlb_range+0x10/0x4c.
>   I wonder why. If you know, please tell me, I naturally
>   have to fix this.
> - The code in kasan_init.c to first back up TTBR0 and then
>   restore it looks *fragile* even if it is working. I think
>   we need to do something better in a per-proc file such
>   as is done in cpu_v7_switch_mm() and other well organized
>   MMU manipulation, I certainly feel this should be done
>   like that.
>
> Abbott Liu (1):
>   ARM: Define the virtual space of KASan's shadow region
>
> Andrey Ryabinin (4):
>   ARM: Disable KASan instrumentation for some code
>   ARM: Replace string mem* functions for KASan
>   ARM: Initialize the mapping of KASan shadow memory
>   ARM: Enable KASan for ARM
>

For the series,

Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Tested-by: Ard Biesheuvel <ardb@kernel.org> # QEMU/KVM/mach-virt/LPAE/8G

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

      parent reply	other threads:[~2020-05-07 17:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 12:45 [PATCH 0/5 v8] KASan for Arm Linus Walleij
2020-05-07 12:45 ` [PATCH 1/5 v8] ARM: Disable KASan instrumentation for some code Linus Walleij
2020-05-07 12:45 ` [PATCH 2/5 v8] ARM: Replace string mem* functions for KASan Linus Walleij
2020-05-07 12:45 ` [PATCH 3/5 v8] ARM: Define the virtual space of KASan's shadow region Linus Walleij
2020-05-07 17:28   ` Ard Biesheuvel
2020-05-07 12:45 ` [PATCH 4/5 v8] ARM: Initialize the mapping of KASan shadow memory Linus Walleij
2020-05-07 12:45 ` [PATCH 5/5 v8] ARM: Enable KASan for ARM Linus Walleij
2020-05-07 17:29 ` Ard Biesheuvel [this message]

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='CAMj1kXGT1WhX=A2q3yH=rOpBcTvXv1-mCujrt_5AAaoATwh9Sw@mail.gmail.com' \
    --to=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=aryabinin@virtuozzo.com \
    --cc=f.fainelli@gmail.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).