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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 01 Feb 2014 11:35:50 -0800
From:	"H. Peter Anvin" <>
To:	Linus Torvalds <>,
	Suresh Siddha <>
CC:	Nate Eldredge <>,
	Thomas Gleixner <>,
	Ingo Molnar <>,
	the arch/x86 maintainers <>,
	stable <>,
	Linux Kernel Mailing List <>,
	Maarten Baert <>,
	Jan Kara <>, George Spelvin <>,
	Pekka Riikonen <>
Subject: Re: [PATCH] Make math_state_restore() save and restore the interrupt

On 02/01/2014 11:27 AM, Linus Torvalds wrote:
>   (a) "we don't want to restore at all, because once the kernel starts
> using math, it might do so a lot, and saving/restoring is a bad idea":
>    void __kernel_fpu_end(void)
>    {
>            stts();
>    }
> *or*
> Quite frankly, I'd almost lean towards (a). Comments? Does anybody
> have any loads where the kernel does a lot of fpu stuff (ie network
> encryption using the hw engines or something)? I'd really like to hear
> if it makes a difference..

This will obviously not protect eageronly features (MPX, LWP, ...) so 
this means those features are permanently unavailable to the kernel, 
even inside kernel_fpu_begin/end.  Now, currently I don't think we have 
any plans to use those in the kernel (at least not in a way where 
kernel_fpu_begin/end makes sense as bracketing), but it is something 
worth keeping in mind.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists