From: Florian Fainelli <f.fainelli@gmail.com>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: alexandre.belloni@bootlin.com, mhocko@suse.com,
catalin.marinas@arm.com, dhowells@redhat.com,
yamada.masahiro@socionext.com, ryabinin.a.a@gmail.com,
glider@google.com, kvmarm@lists.cs.columbia.edu, corbet@lwn.net,
liuwenliang@huawei.com, daniel.lezcano@linaro.org,
linux@armlinux.org.uk, kasan-dev@googlegroups.com,
geert@linux-m68k.org, dvyukov@google.com,
bcm-kernel-feedback-list@broadcom.com, keescook@chromium.org,
arnd@arndb.de, marc.zyngier@arm.com, andre.przywara@arm.com,
pombredanne@nexb.com, jinb.park7@gmail.com, tglx@linutronix.de,
kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org,
nico@fluxnic.net, gregkh@linuxfoundation.org,
ard.biesheuvel@linaro.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rob@landley.net,
philip@cog.systems, akpm@linux-foundation.org,
thgarnie@google.com, kirill.shutemov@linux.intel.com
Subject: Re: [PATCH v6 0/6] KASan for arm
Date: Thu, 14 Nov 2019 15:01:19 -0800 [thread overview]
Message-ID: <7322163f-e08e-a6b7-b143-e9d59917ee5b@gmail.com> (raw)
In-Reply-To: <20191114181243.q37rxoo3seds6oxy@pengutronix.de>
Hello Marco,
On 11/14/19 10:12 AM, Marco Felsch wrote:
> Hi Florian,
>
> first of all, many thanks for your work on this series =) I picked your
> and Arnd patches to make it compilable. Now it's compiling but my imx6q
> board didn't boot anymore. I debugged the code and found that the branch
> to 'start_kernel' won't be reached
>
> 8<------- arch/arm/kernel/head-common.S -------
> ....
>
> #ifdef CONFIG_KASAN
> bl kasan_early_init
> #endif
> mov lr, #0
> b start_kernel
> ENDPROC(__mmap_switched)
>
> ....
> 8<----------------------------------------------
>
> Now, I found also that 'KASAN_SHADOW_OFFSET' isn't set due to missing
> 'CONFIG_KASAN_SHADOW_OFFSET' and so no '-fasan-shadow-offset=xxxxx' is
> added. Can that be the reason why my board isn't booted anymore?
The latest that I have is here, though not yet submitted since I needed
to solve one issue on a specific platform with a lot of memory:
https://github.com/ffainelli/linux/pull/new/kasan-v7
Can you share your branch as well? I did not pick all of Arnd's patches
since some appeared to be seemingly independent from KASan on ARM. This
is the KASAN related options that are set in my configuration:
grep KASAN build/linux-custom/.config
CONFIG_HAVE_ARCH_KASAN=y
CONFIG_CC_HAS_KASAN_GENERIC=y
CONFIG_KASAN=y
CONFIG_KASAN_GENERIC=y
CONFIG_KASAN_OUTLINE=y
# CONFIG_KASAN_INLINE is not set
CONFIG_KASAN_STACK=1
CONFIG_TEST_KASAN=m
are you using something different by any chance?
--
Florian
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2019-11-14 23:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 22:11 [PATCH v6 0/6] KASan for arm Florian Fainelli
2019-06-17 22:11 ` [PATCH v6 1/6] ARM: Add TTBR operator for kasan_init Florian Fainelli
2019-07-02 21:03 ` Linus Walleij
2019-07-11 16:54 ` Florian Fainelli
2019-06-17 22:11 ` [PATCH v6 2/6] ARM: Disable instrumentation for some code Florian Fainelli
2019-07-02 21:56 ` Linus Walleij
2019-07-11 16:53 ` Florian Fainelli
2019-06-17 22:11 ` [PATCH v6 3/6] ARM: Replace memory function for kasan Florian Fainelli
2019-06-17 22:11 ` [PATCH v6 4/6] ARM: Define the virtual space of KASan's shadow region Florian Fainelli
2019-06-17 22:11 ` [PATCH v6 5/6] ARM: Initialize the mapping of KASan shadow memory Florian Fainelli
2019-06-17 22:11 ` [PATCH v6 6/6] ARM: Enable KASan for arm Florian Fainelli
2019-07-02 21:06 ` [PATCH v6 0/6] " Linus Walleij
2019-07-11 17:00 ` Florian Fainelli
2019-07-18 7:51 ` Arnd Bergmann
2019-10-07 21:34 ` Florian Fainelli
2019-10-07 22:10 ` Arnd Bergmann
2019-10-08 8:47 ` Linus Walleij
2019-11-14 18:12 ` Marco Felsch
2019-11-14 23:01 ` Florian Fainelli [this message]
2019-11-15 2:13 ` ***SPAM*** " Matjaz Matjaz
2019-11-15 7:08 ` Marco Felsch
2019-11-15 11:44 ` Marco Felsch
2019-11-19 0:13 ` Florian Fainelli
2020-01-17 10:13 ` Linus Walleij
2020-01-17 19:55 ` Florian Fainelli
2020-01-17 21:05 ` Linus Walleij
2020-03-05 8:43 ` Linus Walleij
2020-03-05 9:43 ` Marco Felsch
2020-03-20 9:26 ` 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=7322163f-e08e-a6b7-b143-e9d59917ee5b@gmail.com \
--to=f.fainelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andre.przywara@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=daniel.lezcano@linaro.org \
--cc=dhowells@redhat.com \
--cc=dvyukov@google.com \
--cc=geert@linux-m68k.org \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jinb.park7@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=kernel@pengutronix.de \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liuwenliang@huawei.com \
--cc=m.felsch@pengutronix.de \
--cc=marc.zyngier@arm.com \
--cc=mhocko@suse.com \
--cc=nico@fluxnic.net \
--cc=philip@cog.systems \
--cc=pombredanne@nexb.com \
--cc=rob@landley.net \
--cc=ryabinin.a.a@gmail.com \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=yamada.masahiro@socionext.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).