linux-kernel - Re: [tip:x86/urgent] x86, fpu: correct the asm constraints for fxsave , unbreak mxcsr.daz

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CA+55aFzVj4YnUMik_BYbSab7PeL=__fPO47FTUAdY2090Yyapg@mail.gmail.com>
Date:	Fri, 26 Jul 2013 14:36:51 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-stable <stable@...r.kernel.org>,
	Peter Anvin <hpa@...ux.intel.com>,
	"H.J. Lu" <hjl.tools@...il.com>, Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"tip-bot for H.J. Lu" <tipbot@...or.com>,
	linux-tip-commits@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [tip:x86/urgent] x86, fpu: correct the asm constraints for fxsave
 , unbreak mxcsr.daz

On Fri, Jul 26, 2013 at 1:19 PM, H. Peter Anvin <hpa@...or.com> wrote:
>
> The bug is obvious; the fix at the very least *should* be obvious; the
> main source of risk would appear that it might trigger bugs in very old
> versions of gcc.

I used to be worried about "+m", but we're using it a lot these days,
and don't support the (really old) versions of gcc that used to have
trouble with in-out constraints. So the fix looks obvious and safe, no
worries from me.

          Linus
--
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/