x86/fpu: Fix invalid FPU ptrace state after execve()
Robert O'Callahan reported that after an execve PTRACE_GETREGSET NT_X86_XSTATE continues to return the pre-exec register values until the exec'ed task modifies FPU state. The test code is at: https://bugzilla.redhat.com/attachment.cgi?id=1164286. What is happening is fpu__clear() does not properly clear fpstate. Fix it by doing just that. Reported-by: Robert O'Callahan <robert@ocallahan.org> Signed-off-by: Yu-cheng Yu <yu-cheng.yu@intel.com> Cc: <stable@vger.kernel.org> Cc: Andy Lutomirski <luto@kernel.org> Cc: Borislav Petkov <bp@suse.de> Cc: David Hansen <dave.hansen@linux.intel.com> Cc: Fenghua Yu <fenghua.yu@intel.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Ravi V. Shankar <ravi.v.shankar@intel.com> Cc: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/1479402695-6553-1-git-send-email-yu-cheng.yu@intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
This commit is contained in:
parent
ed68d7e9b9
commit
b22cbe404a
|
@ -521,14 +521,14 @@ void fpu__clear(struct fpu *fpu)
|
||||||
{
|
{
|
||||||
WARN_ON_FPU(fpu != ¤t->thread.fpu); /* Almost certainly an anomaly */
|
WARN_ON_FPU(fpu != ¤t->thread.fpu); /* Almost certainly an anomaly */
|
||||||
|
|
||||||
if (!use_eager_fpu() || !static_cpu_has(X86_FEATURE_FPU)) {
|
fpu__drop(fpu);
|
||||||
/* FPU state will be reallocated lazily at the first use. */
|
|
||||||
fpu__drop(fpu);
|
/*
|
||||||
} else {
|
* Make sure fpstate is cleared and initialized.
|
||||||
if (!fpu->fpstate_active) {
|
*/
|
||||||
fpu__activate_curr(fpu);
|
if (static_cpu_has(X86_FEATURE_FPU)) {
|
||||||
user_fpu_begin();
|
fpu__activate_curr(fpu);
|
||||||
}
|
user_fpu_begin();
|
||||||
copy_init_fpstate_to_fpregs();
|
copy_init_fpstate_to_fpregs();
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue