From: Will Deacon <will.deacon@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Dave Martin" <Dave.Martin@arm.com>,
"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
"Catalin Marinas" <Catalin.Marinas@arm.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: arm64: unhandled level 0 translation fault
Date: Fri, 15 Dec 2017 14:27:32 +0000 [thread overview]
Message-ID: <20171215142732.GL25650@arm.com> (raw)
In-Reply-To: <CAMuHMdWio0KnJc3DQeQyf-MHpDC=tc3cJLNK7MmaL=MdDz45UQ@mail.gmail.com>
On Fri, Dec 15, 2017 at 02:30:00PM +0100, Geert Uytterhoeven wrote:
> On Fri, Dec 15, 2017 at 12:23 PM, Dave Martin <Dave.Martin@arm.com> wrote:
> > The two important differences here seem to be
> >
> > 1) Staging the state via current->thread.fpsimd_state instead of loading
> > directly:
> >
> > - fpsimd_load_state(state);
> > + current->thread.fpsimd_state = *state;
> > + fpsimd_load_state(¤t->thread.fpsimd_state);
>
> The change above introduces the breakage.
I finally managed to reproduce this, but only by using the exact same
compiler as Geert:
https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.9.0/x86_64-gcc-4.9.0-nolibc_aarch64-linux.tar.xz
I then reliably see the problem if I run:
# /usr/bin/update-ca-certificates
from Debian Jessie.
Note that my normal toolchain (Linaro 7.1.1 build) works fine and also
if I use the toolchain above but disable CONFIG_ARM64_CRYPTO then things
work too.
So there's some toolchain-specific interaction between this change and the
crypto code...
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64: unhandled level 0 translation fault
Date: Fri, 15 Dec 2017 14:27:32 +0000 [thread overview]
Message-ID: <20171215142732.GL25650@arm.com> (raw)
In-Reply-To: <CAMuHMdWio0KnJc3DQeQyf-MHpDC=tc3cJLNK7MmaL=MdDz45UQ@mail.gmail.com>
On Fri, Dec 15, 2017 at 02:30:00PM +0100, Geert Uytterhoeven wrote:
> On Fri, Dec 15, 2017 at 12:23 PM, Dave Martin <Dave.Martin@arm.com> wrote:
> > The two important differences here seem to be
> >
> > 1) Staging the state via current->thread.fpsimd_state instead of loading
> > directly:
> >
> > - fpsimd_load_state(state);
> > + current->thread.fpsimd_state = *state;
> > + fpsimd_load_state(¤t->thread.fpsimd_state);
>
> The change above introduces the breakage.
I finally managed to reproduce this, but only by using the exact same
compiler as Geert:
https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.9.0/x86_64-gcc-4.9.0-nolibc_aarch64-linux.tar.xz
I then reliably see the problem if I run:
# /usr/bin/update-ca-certificates
from Debian Jessie.
Note that my normal toolchain (Linaro 7.1.1 build) works fine and also
if I use the toolchain above but disable CONFIG_ARM64_CRYPTO then things
work too.
So there's some toolchain-specific interaction between this change and the
crypto code...
Will
next prev parent reply other threads:[~2017-12-15 14:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 10:20 arm64: unhandled level 0 translation fault Geert Uytterhoeven
2017-12-12 10:20 ` Geert Uytterhoeven
2017-12-12 10:36 ` Will Deacon
2017-12-12 10:36 ` Will Deacon
2017-12-12 15:11 ` Geert Uytterhoeven
2017-12-12 15:11 ` Geert Uytterhoeven
2017-12-12 16:00 ` Geert Uytterhoeven
2017-12-12 16:00 ` Geert Uytterhoeven
2017-12-12 16:57 ` Will Deacon
2017-12-12 16:57 ` Will Deacon
2017-12-12 20:54 ` Geert Uytterhoeven
2017-12-12 20:54 ` Geert Uytterhoeven
2017-12-13 10:24 ` Will Deacon
2017-12-13 10:24 ` Will Deacon
2017-12-14 14:34 ` Geert Uytterhoeven
2017-12-14 14:34 ` Geert Uytterhoeven
2017-12-14 15:16 ` Will Deacon
2017-12-14 15:16 ` Will Deacon
2017-12-14 15:24 ` Dave P Martin
2017-12-14 15:24 ` Dave P Martin
2017-12-14 18:08 ` Geert Uytterhoeven
2017-12-14 18:08 ` Geert Uytterhoeven
2017-12-15 11:23 ` Dave Martin
2017-12-15 11:23 ` Dave Martin
2017-12-15 13:30 ` Geert Uytterhoeven
2017-12-15 13:30 ` Geert Uytterhoeven
2017-12-15 14:27 ` Will Deacon [this message]
2017-12-15 14:27 ` Will Deacon
2017-12-15 15:56 ` Geert Uytterhoeven
2017-12-15 15:56 ` Geert Uytterhoeven
2017-12-15 15:59 ` Geert Uytterhoeven
2017-12-15 15:59 ` Geert Uytterhoeven
2017-12-15 16:06 ` Will Deacon
2017-12-15 16:06 ` Will Deacon
2017-12-15 17:11 ` Dave Martin
2017-12-15 17:11 ` Dave Martin
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=20171215142732.GL25650@arm.com \
--to=will.deacon@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Dave.Martin@arm.com \
--cc=alex.bennee@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.