From: Guenter Roeck <linux@roeck-us.net>
To: Paul Burton <paul.burton@imgtec.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org
Subject: Re: Crash in -next due to 'MIPS: Move FP usage checks into protected_{save, restore}_fp_context'
Date: Mon, 27 Jul 2015 13:41:04 -0700 [thread overview]
Message-ID: <20150727204104.GA1198@roeck-us.net> (raw)
In-Reply-To: <20150727200214.GH7289@NP-P-BURTON>
Hi Paul,
On Mon, Jul 27, 2015 at 01:02:14PM -0700, Paul Burton wrote:
>
> Hi Guenter,
>
> I'm currently mailing out v2 of the series which should fix your
> problem. It was an issue where the kernel would check the FP context for
> whether a SIGFPE should be generated even in cases where FP had not been
> used by userland, and thus had not been initialised. My userland is
> hard float & thus makes use of the FPU early whilst I believe yours is
> soft float, which explains the difference in behaviour.
>
> I think the endian difference probably boils down to what garbage the
> initial FP context contained.
>
Thanks a lot for the fix!
Guenter
next prev parent reply other threads:[~2015-07-27 20:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 16:09 Crash in -next due to 'MIPS: Move FP usage checks into protected_{save, restore}_fp_context' Guenter Roeck
2015-07-27 15:06 ` Guenter Roeck
2015-07-27 17:21 ` Paul Burton
2015-07-27 17:21 ` Paul Burton
2015-07-27 17:46 ` Guenter Roeck
2015-07-27 18:04 ` Paul Burton
2015-07-27 18:04 ` Paul Burton
2015-07-27 18:17 ` Guenter Roeck
2015-07-27 19:44 ` Guenter Roeck
2015-07-27 20:02 ` Paul Burton
2015-07-27 20:02 ` Paul Burton
2015-07-27 20:41 ` Guenter Roeck [this message]
2015-07-28 8:31 ` Ralf Baechle
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=20150727204104.GA1198@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-next@vger.kernel.org \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.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.