linux-kernel - x86 fpu: command-line parameters broken post-FPU-rewrite

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-next>] [day] [month] [year] [list]

Date:	Tue, 8 Dec 2015 12:43:13 -0800
From:	Dave Hansen <dave.hansen@...el.com>
To:	Ingo Molnar <mingo@...nel.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"Yu, Yu-cheng" <yu-cheng.yu@...el.com>,
	"Yu, Fenghua" <fenghua.yu@...el.com>
Subject: x86 fpu: command-line parameters broken post-FPU-rewrite

Hey Ingo,

We were starting to look at reenabling XSAVES support and tried to use
the 'noxsave' and 'noxsaves' kernel command-line options.  The rewrite
moved the FPU initialization to before we even are parsing command-line
options, even the early_param()s.

Do you have any preferences on how it gets fixed?

The most obvious thing would be to just defer as much of the FPU setup
as we can until after parse_early_param() has happened.  The only other
think I can think of doing would be to try to do some *really* early,
simple, command-line parsing to look for 'noxsave' and friends.

Thoughts?
--
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/