This is a note to let you know that I've just added the patch titled
powerpc: Add security feature flags for Spectre/Meltdown
to the 4.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the pat
commit 9a868f634349e62922c226834aa23e3d1329ae7f upstream.
This commit adds security feature flags to reflect the settings we
receive from firmware regarding Spectre/Meltdown mitigations.
The feature names reflect the names we are given by firmware on bare
metal machines. See the hostboot source
On 23. Nov 2018, at 19:59, Michal Suchánek wrote:
With this summary paper https://arxiv.org/abs/1811.05441 it should be
possible to take the manual for your favourite CPU and see which
exploitable optimizations it does have, and how are these exploits
mitigated.
Thanks
Michal
Hi Michal,
Than
On Wed, 10 Jan 2018 18:09:45 -0600
Li Yang wrote:
Hello,
> On Mon, Jan 8, 2018 at 2:17 AM, Christian Zigotzky
> wrote:
> > Hi All,
> >
> > Thanks a lot for your replies.
> >
> > @NXP developers: Could you please tell us some information?
>
> We have done some investigation but it is not read
This is a note to let you know that I've just added the patch titled
powerpc: Add security feature flags for Spectre/Meltdown
to the 4.9-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the pat
commit 9a868f634349e62922c226834aa23e3d1329ae7f upstream.
This commit adds security feature flags to reflect the settings we
receive from firmware regarding Spectre/Meltdown mitigations.
The feature names reflect the names we are given by firmware on bare
metal machines. See the hostboot source
This is a note to let you know that I've just added the patch titled
powerpc: Add security feature flags for Spectre/Meltdown
to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the pat
commit 9a868f634349e62922c226834aa23e3d1329ae7f upstream.
This commit adds security feature flags to reflect the settings we
receive from firmware regarding Spectre/Meltdown mitigations.
The feature names reflect the names we are given by firmware on bare
metal machines. See the hostboot source
This commit adds security feature flags to reflect the settings we
receive from firmware regarding Spectre/Meltdown mitigations.
The feature names reflect the names we are given by firmware on bare
metal machines. See the hostboot source for details.
Arguably these could be firmware features
This is a note to let you know that I've just added the patch titled
powerpc: Add security feature flags for Spectre/Meltdown
to the 4.16-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the pat
commit 9a868f634349e62922c226834aa23e3d1329ae7f upstream.
This commit adds security feature flags to reflect the settings we
receive from firmware regarding Spectre/Meltdown mitigations.
The feature names reflect the names we are given by firmware on bare
metal machines. See the hostboot source
On Tue, 2018-03-27 at 12:01:44 UTC, Michael Ellerman wrote:
> This commit adds security feature flags to reflect the settings we
> receive from firmware regarding Spectre/Meltdown mitigations.
>
> The feature names reflect the names we are given by firmware on bare
> metal ma
On Tue, Mar 27, 2018 at 11:01:44PM +1100, Michael Ellerman wrote:
> This commit adds security feature flags to reflect the settings we
> receive from firmware regarding Spectre/Meltdown mitigations.
>
> The feature names reflect the names we are given by firmware on bare
> metal ma
This commit adds security feature flags to reflect the settings we
receive from firmware regarding Spectre/Meltdown mitigations.
The feature names reflect the names we are given by firmware on bare
metal machines. See the hostboot source for details.
Arguably these could be firmware features
/commits/Michael-Ellerman/powerpc-Add-security-feature-flags-for-Spectre-Meltdown/20180327-041008
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
config: powerpc-g5_defconfig (attached as .config)
compiler: powerpc64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce
This commit adds security feature flags to reflect the settings we
receive from firmware regarding Spectre/Meltdown mitigations.
The feature names reflect the names we are given by firmware on bare
metal machines. See the hostboot source for details.
Arguably these could be firmware features
powerpc/include/asm/security_features.h
>> @@ -0,0 +1,65 @@
...
>> +// Features indicating support for Spectre/Meltdown mitigations
>> +
>> +// The L1-D cache can be flushed with ori r30,r30,0
>> +#define SEC_FTR_L1D_FLUSH_ORI30 0x0001ull
>>
Segher Boessenkool writes:
> Hi!
>
> On Thu, Mar 01, 2018 at 01:53:11AM +1100, Michael Ellerman wrote:
>> +// A speculation barrier should be used for bounds checks (Spectre variant
>> 1ull
>
> s/1ull/1)/ ?
Haha, oops. Thanks for spotting it.
Result of replacing ASM_CONST(x) with xull.
cheer
Michael Ellerman writes:
> This commit adds security feature flags to reflect the settings we
> receive from firmware regarding Spectre/Meltdown mitigations.
>
> The feature names reflect the names we are given by firmware on bare
> metal machines. See the hostboot sou
Hi!
On Thu, Mar 01, 2018 at 01:53:11AM +1100, Michael Ellerman wrote:
> +// A speculation barrier should be used for bounds checks (Spectre variant
> 1ull
s/1ull/1)/ ?
Segher
This commit adds security feature flags to reflect the settings we
receive from firmware regarding Spectre/Meltdown mitigations.
The feature names reflect the names we are given by firmware on bare
metal machines. See the hostboot source for details.
Arguably these could be firmware features
On Mon, Jan 8, 2018 at 2:17 AM, Christian Zigotzky
wrote:
> Hi All,
>
> Thanks a lot for your replies.
>
> @NXP developers: Could you please tell us some information?
We have done some investigation but it is not ready to be published
yet. You can get more information from your support channel r
Hi All,
Thanks a lot for your replies.
@NXP developers: Could you please tell us some information?
Thanks,
Christian
On 08 January 2018 at 02:14AM, Michal Suchanek wrote:
On 7 January 2018 at 19:54, Olof Johansson wrote:
On Sun, Jan 7, 2018 at 5:04 AM, Christian Zigotzky
wrote:
Hello Mic
On 7 January 2018 at 19:54, Olof Johansson wrote:
> On Sun, Jan 7, 2018 at 5:04 AM, Christian Zigotzky
> wrote:
>> Hello Michael,
>>
>> Thanks for your reply. We are using P.A. Semi and Freescale CPUs.
>>
>> @Olof
>> Do you have some infos for us?
>
> I'm low on spare time to experiment and explo
On Sun, Jan 7, 2018 at 5:04 AM, Christian Zigotzky
wrote:
> Hello Michael,
>
> Thanks for your reply. We are using P.A. Semi and Freescale CPUs.
>
> @Olof
> Do you have some infos for us?
I'm low on spare time to experiment and explore what might be exposed
or not, and I no longer have any propri
Hello Michael,
Thanks for your reply. We are using P.A. Semi and Freescale CPUs.
@Olof
Do you have some infos for us?
Thanks,
Christian
On 06/01/18 10:34, Michael Ellerman wrote:
Christian Zigotzky writes:
Hi All,
Do we have some information regarding Spectre+Meltdown for our users?
It
Christian Zigotzky writes:
> 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.
There's a statement from IBM here:
https://www.ibm.com/blogs/psirt/potential-impact-pro
Hello,
On Thu, 4 Jan 2018 16:09:34 +0100
Christian Zigotzky 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
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&am
29 matches
Mail list logo
