* Re: [PATCH 4.9 34/77] powerpc: fix build errors in stable tree
[not found] ` <1519306335.2388.18.camel@debian.org>
@ 2018-02-22 22:31 ` Michael Ellerman
0 siblings, 0 replies; only message in thread
From: Michael Ellerman @ 2018-02-22 22:31 UTC (permalink / raw)
To: Yves-Alexis Perez, Greg Kroah-Hartman, linux-kernel
Cc: stable, Guenter Roeck, Nicholas Piggin, linuxppc-dev
Yves-Alexis Perez <corsac@debian•org> writes:
> On Fri, 2018-02-23 at 00:16 +1100, Michael Ellerman wrote:
>> With the patches I just sent, for pseries and powernv, the mitigation
>> should be in place. On machines with updated firmware we'll use the
>> hardware-assisted L1 flush, otherwise we fallback to doing it in
>> software.
>
> So as of 4.9.82 meltdown is *not* addressed on those arches, but it should be
> ok in 4.9.83 or 4.9.84 depending on when the patches are merged?
As of 4.9.82 *most* of the patches to do the mitigation have been
merged.
One of them was missed, due to it not applying (because it was actually
a back port to 4.4 that was sent) that is:
222f20f14062 ("powerpc/64s: Simple RFI macro conversions")
That patch adds calls to do the L1D cache flush when returning to
user/guest, so it is important that it's missing, the mitigation is not
fully effective without that patch.
However, 4.9.82 *does* have a backport of:
b8e90cb7bc04 ("powerpc/64: Convert the syscall exit path to use RFI_TO_USER/KERNEL")
So the syscall path is protected, which means any attack which uses
syscalls is likely to fail.
Because the data the attack is trying to read has to be in the L1D, you
can't write an attack that remains in userspace 100% of the time, you
have to enter the kernel and have the kernel load the target data into
the L1D for you. With the syscall flush in place you can't use a syscall
for that, you have to trigger some other kernel entry/exit, eg. a page
fault.
TLDR is with the syscall flush in place it's much harder to write an
attack.
Greg has already released 4.9.83, so hopefully 4.9.84 will be fully
protected.
Note also that 4.9.82/83 have a bug in the SLB miss handler that can
lead to hangs in userspace, fixed by the first patch I sent.
cheers
^ permalink raw reply [flat|nested] only message in thread