path: root/fs
diff options
authorBobby Powers <>2015-04-27 08:10:41 -0700
committerIngo Molnar <>2015-05-06 11:22:03 +0200
commitc88d47480d300eaad80c213d50c9bf6077fc49bc (patch)
tree51a9a595a1fb7ab9eb665945536a46efb2f00666 /fs
parentc102cb097d9371c2c60049d041ab1f8bdca5ccc2 (diff)
x86/fpu: Always restore_xinit_state() when use_eager_cpu()
The following commit: f893959b0898 ("x86/fpu: Don't abuse drop_init_fpu() in flush_thread()") removed drop_init_fpu() usage from flush_thread(). This seems to break things for me - the Go 1.4 test suite fails all over the place with floating point comparision errors (offending commit found through bisection). The functional change was that flush_thread() after this commit only calls restore_init_xstate() when both use_eager_fpu() and !used_math() are true. drop_init_fpu() (now fpu_reset_state()) calls restore_init_xstate() regardless of whether current used_math() - apply the same logic here. Switch used_math() -> tsk_used_math(tsk) to consistently use the grabbed tsk instead of current, like in the rest of flush_thread(). Tested-by: Dave Hansen <> Signed-off-by: Bobby Powers <> Signed-off-by: Borislav Petkov <> Acked-by: Oleg Nesterov <> Cc: Andy Lutomirski <> Cc: Borislav Petkov <> Cc: Fenghua Yu <> Cc: H. Peter Anvin <> Cc: Linus Torvalds <> Cc: Pekka Riikonen <> Cc: Quentin Casasnovas <> Cc: Rik van Riel <> Cc: Suresh Siddha <> Cc: Thomas Gleixner <> Fixes: f893959b ("x86/fpu: Don't abuse drop_init_fpu() in flush_thread()") Link: Signed-off-by: Ingo Molnar <>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions