linux-kernel - Re: Crash in -next due to 'MIPS: Move FP usage checks into protected_{save, restore}_fp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150727204104.GA1198@roeck-us.net>
Date:	Mon, 27 Jul 2015 13:41:04 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Paul Burton <paul.burton@...tec.com>
Cc:	Ralf Baechle <ralf@...ux-mips.org>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org
Subject: Re: Crash in -next due to 'MIPS: Move FP usage checks into
 protected_{save, restore}_fp_context'

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/