From: "Michal Suchánek" <msuchanek@suse.de>
To: Christian Zigotzky <chzigotzky@xenosoft.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Spectre+Meltdown
Date: Thu, 4 Jan 2018 22:27:04 +0100 [thread overview]
Message-ID: <20180104222704.5a9b490d@naga.suse.cz> (raw)
In-Reply-To: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de>
Hello,
On Thu, 4 Jan 2018 16:09:34 +0100
Christian Zigotzky <chzigotzky@xenosoft.de> wrote:
> Hi All,
>
> Do we have some information regarding Spectre+Meltdown for our users?
>
> It could be that we have some security issues in our PowerPC CPUs.
>
> Links:
>
> https://www.phoronix.com/scan.php?page=news_item&px=Linux-Kernel-Retpoline-Patches
>
> https://www.phoronix.com/scan.php?page=news_item&px=x86-PTI-EPYC-Linux-4.15-Test
>
Since the vulnerability details were disclosed already you should see
patches addressing it in your local kernel git repository. AFAICT some
patches for preventing speculative execution in some random parts of
the kernel as well as adding an extra flush when returning from kernel
to userspace are applicable to powerpc.
I am not familiar with all the details so you are free to investigate
the code for yourself or fish some article from someone who really
knows what the thing is all about and how it affects powerpc in
particular.
Thanks
Michal
next prev parent reply other threads:[~2018-01-04 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 15:09 Spectre+Meltdown Christian Zigotzky
2018-01-04 21:27 ` Michal Suchánek [this message]
2018-01-06 9:34 ` Spectre+Meltdown Michael Ellerman
2018-01-07 13:04 ` Spectre+Meltdown Christian Zigotzky
2018-01-07 18:54 ` Spectre+Meltdown Olof Johansson
2018-01-08 1:14 ` Spectre+Meltdown Michal Suchanek
2018-01-08 8:17 ` Spectre+Meltdown Christian Zigotzky
2018-01-11 0:09 ` Spectre+Meltdown Li Yang
2018-11-23 18:59 ` Spectre+Meltdown Michal Suchánek
2018-11-24 9:14 ` Spectre+Meltdown Christian Zigotzky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180104222704.5a9b490d@naga.suse.cz \
--to=msuchanek@suse.de \
--cc=chzigotzky@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox