Re: [PATCH 22/22] x86/mm: zero stack on stack switch or reset

2024-09-27 Thread Roger Pau Monné
On Tue, Aug 13, 2024 at 03:16:42PM +0200, Jan Beulich wrote: > On 26.07.2024 17:22, Roger Pau Monne wrote: > > With the stack mapped on a per-CPU basis there's no risk of other CPUs being > > able to read the stack contents, but vCPUs running on the current pCPU could > > read stack rubble from ope

Re: [PATCH 22/22] x86/mm: zero stack on stack switch or reset

2024-08-13 Thread Jan Beulich
On 26.07.2024 17:22, Roger Pau Monne wrote: > With the stack mapped on a per-CPU basis there's no risk of other CPUs being > able to read the stack contents, but vCPUs running on the current pCPU could > read stack rubble from operations of previous vCPUs. > > The #DF stack is not zeroed because h

Re: [PATCH 22/22] x86/mm: zero stack on stack switch or reset

2024-07-30 Thread Roger Pau Monné
On Mon, Jul 29, 2024 at 04:40:24PM +0100, Andrew Cooper wrote: > On 26/07/2024 4:22 pm, Roger Pau Monne wrote: > > With the stack mapped on a per-CPU basis there's no risk of other CPUs being > > able to read the stack contents, but vCPUs running on the current pCPU could > > read stack rubble from

Re: [PATCH 22/22] x86/mm: zero stack on stack switch or reset

2024-07-29 Thread Andrew Cooper
On 26/07/2024 4:22 pm, Roger Pau Monne wrote: > With the stack mapped on a per-CPU basis there's no risk of other CPUs being > able to read the stack contents, but vCPUs running on the current pCPU could > read stack rubble from operations of previous vCPUs. > > The #DF stack is not zeroed because

[PATCH 22/22] x86/mm: zero stack on stack switch or reset

2024-07-26 Thread Roger Pau Monne
With the stack mapped on a per-CPU basis there's no risk of other CPUs being able to read the stack contents, but vCPUs running on the current pCPU could read stack rubble from operations of previous vCPUs. The #DF stack is not zeroed because handling of #DF results in a panic. Signed-off-by: Rog