From: Ard Biesheuvel <ardb@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Abbott Liu <liuwenliang@huawei.com>,
Linus Walleij <linus.walleij@linaro.org>,
Russell King <linux@armlinux.org.uk>,
Mike Rapoport <rppt@linux.ibm.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/5 v11] KASan for Arm
Date: Wed, 1 Jul 2020 23:41:09 +0200 [thread overview]
Message-ID: <CAMj1kXEfo1JzxVNYFzaA89-u2R5=eroiA+kpMBCxq67z9fYXmA@mail.gmail.com> (raw)
In-Reply-To: <89cd5038-8dfb-bddf-da1d-b1f412158ae4@gmail.com>
On Wed, 1 Jul 2020 at 22:16, Florian Fainelli <f.fainelli@gmail.com> wrote:
>
>
>
> On 7/1/2020 5:09 AM, Ard Biesheuvel wrote:
> >
> > I pushed these changes and a few more to
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=arm-kasan-v11
>
> This branch works a bit better however I am still seeing some boot
> errors (some sample logs attached) similar to Linus' branch.
>
These crashes are all identical, they all crash on the bc9ffe00 shadow
address not being backed by early shadow memory.
That value has all bits PTE index bits set to 1, and given how
memblock usually allocates top down, it means we are allocating page
by page and calling check_memory_region() on it during the memset()
until the point where we hit a PMD that is not set, covering the
window bc800000-bc9fffff
Are there any memory reservations in the range ec000000-ecffffff ? Are
you using the default vmalloc range? Any other peculiarities in the
memory layout?
_______________________________________________
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-07-01 21:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 13:37 [PATCH 0/5 v11] KASan for Arm Linus Walleij
2020-06-30 13:37 ` [PATCH 1/5 v11] ARM: Disable KASan instrumentation for some code Linus Walleij
2020-06-30 13:37 ` [PATCH 2/5 v11] ARM: Replace string mem* functions for KASan Linus Walleij
2020-06-30 13:37 ` [PATCH 3/5 v11] ARM: Define the virtual space of KASan's shadow region Linus Walleij
2020-06-30 13:37 ` [PATCH 4/5 v11] ARM: Initialize the mapping of KASan shadow memory Linus Walleij
2020-06-30 13:37 ` [PATCH 5/5 v11] ARM: Enable KASan for ARM Linus Walleij
2020-06-30 16:54 ` [PATCH 0/5 v11] KASan for Arm Florian Fainelli
2020-06-30 21:41 ` Ard Biesheuvel
2020-07-01 4:53 ` Florian Fainelli
2020-07-01 7:43 ` Ard Biesheuvel
2020-07-01 8:32 ` Ard Biesheuvel
2020-07-01 12:09 ` Ard Biesheuvel
2020-07-01 20:16 ` Florian Fainelli
2020-07-01 21:41 ` Ard Biesheuvel [this message]
2020-07-01 22:28 ` Florian Fainelli
2020-07-01 23:03 ` Ard Biesheuvel
2020-07-03 3:36 ` Florian Fainelli
2020-07-03 6:41 ` Ard Biesheuvel
2020-07-06 13:08 ` Linus Walleij
2020-07-10 15:09 ` Linus Walleij
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='CAMj1kXEfo1JzxVNYFzaA89-u2R5=eroiA+kpMBCxq67z9fYXmA@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 \
--cc=rppt@linux.ibm.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).