Patch "powerpc/security: Fix spectre_v2 reporting" has been added to the 4.4-stable tree

2019-04-29 Thread gregkh
This is a note to let you know that I've just added the patch titled powerpc/security: Fix spectre_v2 reporting 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 patch is: po

[PATCH stable v4.4 51/52] powerpc/security: Fix spectre_v2 reporting

2019-04-21 Thread Michael Ellerman
commit 92edf8df0ff2ae86cc632eeca0e651fd8431d40d upstream. When I updated the spectre_v2 reporting to handle software count cache flush I got the logic wrong when there's no software count cache enabled at all. The result is that on systems with the software count cache flush disabled we print:

[PATCH stable v4.9 35/35] powerpc/security: Fix spectre_v2 reporting

2019-04-11 Thread Michael Ellerman
commit 92edf8df0ff2ae86cc632eeca0e651fd8431d40d upstream. When I updated the spectre_v2 reporting to handle software count cache flush I got the logic wrong when there's no software count cache enabled at all. The result is that on systems with the software count cache flush disabled we print:

Patch "powerpc/security: Fix spectre_v2 reporting" has been added to the 4.19-stable tree

2019-03-29 Thread gregkh
This is a note to let you know that I've just added the patch titled powerpc/security: Fix spectre_v2 reporting to the 4.19-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 patch is: po

Patch "[PATCH stable v4.14 32/32] powerpc/security: Fix spectre_v2 reporting" has been added to the 4.14-stable tree

2019-03-29 Thread gregkh
This is a note to let you know that I've just added the patch titled [PATCH stable v4.14 32/32] powerpc/security: Fix spectre_v2 reporting 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 filena

[PATCH stable v4.14 32/32] powerpc/security: Fix spectre_v2 reporting

2019-03-29 Thread Michael Ellerman
commit 92edf8df0ff2ae86cc632eeca0e651fd8431d40d upstream. When I updated the spectre_v2 reporting to handle software count cache flush I got the logic wrong when there's no software count cache enabled at all. The result is that on systems with the software count cache flush disabled we print:

Re: powerpc/security: Fix spectre_v2 reporting

2019-03-22 Thread Michael Ellerman
On Thu, 2019-03-21 at 04:24:33 UTC, Michael Ellerman wrote: > When I updated the spectre_v2 reporting to handle software count cache > flush I got the logic wrong when there's no software count cache > enabled at all. > > The result is that on systems with the software count cache flush > disabled

Re: [PATCH] powerpc/security: Fix spectre_v2 reporting

2019-03-21 Thread Diana Madalina Craciun
Reviewed-by: Diana Craciun On 3/21/2019 6:24 AM, Michael Ellerman wrote: > When I updated the spectre_v2 reporting to handle software count cache > flush I got the logic wrong when there's no software count cache > enabled at all. > > The result is that on systems with the software count cache fl

Re: [PATCH] powerpc/security: Fix spectre_v2 reporting

2019-03-20 Thread Michael Neuling
On Thu, 2019-03-21 at 15:24 +1100, Michael Ellerman wrote: > When I updated the spectre_v2 reporting to handle software count cache > flush I got the logic wrong when there's no software count cache > enabled at all. > > The result is that on systems with the software count cache flush > disabled

[PATCH] powerpc/security: Fix spectre_v2 reporting

2019-03-20 Thread Michael Ellerman
When I updated the spectre_v2 reporting to handle software count cache flush I got the logic wrong when there's no software count cache enabled at all. The result is that on systems with the software count cache flush disabled we print: Mitigation: Indirect branch cache disabled, Software count