Re: [PATCH 4/3] x86/fpu: don't use current->mm to check for a kthread

2019-06-13 Thread Borislav Petkov
On Tue, Jun 04, 2019 at 07:54:12PM +0200, Christoph Hellwig wrote: > current->mm can be non-NULL if a kthread calls use_mm. Check for > PF_KTHREAD instead to decide when to store user mode FP state. > > Fixes: 2722146eb784 ("x86/fpu: Remove fpu->initialized") > Reported-by: Peter Zijlstra > Sign

Re: [PATCH 4/3] x86/fpu: don't use current->mm to check for a kthread

2019-06-11 Thread Sebastian Andrzej Siewior
On 2019-06-04 19:54:12 [+0200], Christoph Hellwig wrote: > current->mm can be non-NULL if a kthread calls use_mm. Check for > PF_KTHREAD instead to decide when to store user mode FP state. > > Fixes: 2722146eb784 ("x86/fpu: Remove fpu->initialized") > Reported-by: Peter Zijlstra > Signed-off-by:

[PATCH 4/3] x86/fpu: don't use current->mm to check for a kthread

2019-06-04 Thread Christoph Hellwig
current->mm can be non-NULL if a kthread calls use_mm. Check for PF_KTHREAD instead to decide when to store user mode FP state. Fixes: 2722146eb784 ("x86/fpu: Remove fpu->initialized") Reported-by: Peter Zijlstra Signed-off-by: Christoph Hellwig --- arch/x86/include/asm/fpu/internal.h | 6 +++-