diff options
| author | Suresh Siddha <suresh.b.siddha@intel.com> | 2008-03-03 13:01:08 -0800 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2008-03-04 17:10:12 +0100 |
| commit | 18a8622101154277df97e24097ed17aace84fa3a (patch) | |
| tree | 3e0581e849c67539b9695b88fc08a68b811cd9e5 /arch/x86/kernel/paravirt_patch_64.c | |
| parent | 976dde010e513a9c7c3117a32b7b015f84b37430 (diff) | |
x86, i387: fix ptrace leakage using init_fpu()
This bug got introduced by the recent i387 merge:
commit 4421011120b2304e5c248ae4165a2704588aedf1
Author: Roland McGrath <roland@redhat.com>
Date: Wed Jan 30 13:31:50 2008 +0100
x86: x86 i387 user_regset
Current usage of unlazy_fpu() in ptrace specific routines is wrong.
unlazy_fpu() will not init fpu if the task never used math. So the
ptrace calls can expose the parent tasks FPU data in some cases.
Replace it with the init_fpu() which will init the math state, if the
task never used math before.
Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'arch/x86/kernel/paravirt_patch_64.c')
0 files changed, 0 insertions, 0 deletions