[PATCH 16/22] x86/fpu: Always store the registers in copy_fpstate_to_sigframe()

2019-02-21 Thread Sebastian Andrzej Siewior
From: Rik van Riel copy_fpstate_to_sigframe() stores the registers directly to user space. This is okay because the FPU register are valid and saving it directly avoids saving it into kernel memory and making a copy. However… We can't keep doing this if we are going to restore the FPU registers o

Re: [PATCH 16/22] x86/fpu: Always store the registers in copy_fpstate_to_sigframe()

2019-02-07 Thread Sebastian Andrzej Siewior
On 2019-01-30 12:43:22 [+0100], Borislav Petkov wrote: > > @@ -171,9 +156,15 @@ int copy_fpstate_to_sigframe(void __user *buf, void > > __user *buf_fx, int size) > > sizeof(struct user_i387_ia32_struct), NULL, > > (struct _fpstate_32 __user *) buf) ? -1 : 1;

Re: [PATCH 16/22] x86/fpu: Always store the registers in copy_fpstate_to_sigframe()

2019-01-30 Thread Borislav Petkov
On Wed, Jan 09, 2019 at 12:47:38PM +0100, Sebastian Andrzej Siewior wrote: > From: Rik van Riel > > copy_fpstate_to_sigframe() stores the registers directly to user space. > This is okay because the FPU register are valid and saving it directly > avoids saving it into kernel memory and making a c

[PATCH 16/22] x86/fpu: Always store the registers in copy_fpstate_to_sigframe()

2019-01-09 Thread Sebastian Andrzej Siewior
From: Rik van Riel copy_fpstate_to_sigframe() stores the registers directly to user space. This is okay because the FPU register are valid and saving it directly avoids saving it into kernel memory and making a copy. However… We can't keep doing this if we are going to restore the FPU registers o