linux-kernel - Re: [Xen-devel] [PATCH] x86/xen: zero MSR_IA32_SPEC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <5ACF2CB002000078001BA984@prv1-mh.provo.novell.com>
Date:   Thu, 12 Apr 2018 01:53:52 -0600
From:   "Jan Beulich" <JBeulich@...e.com>
To:     "Ingo Molnar" <mingo@...nel.org>
Cc:     <x86@...nel.org>, <tglx@...utronix.de>,
        <xen-devel@...ts.xenproject.org>, <boris.ostrovsky@...cle.com>,
        <mingo@...hat.com>, "Juergen Gross" <jgross@...e.com>,
        <linux-kernel@...r.kernel.org>, <stable@...r.kernel.org>,
        <hpa@...or.com>
Subject: Re: [Xen-devel] [PATCH] x86/xen: zero MSR_IA32_SPEC_CTRL
 before suspend

>>> On 12.04.18 at 09:32, <mingo@...nel.org> wrote:

> * Jan Beulich <JBeulich@...e.com> wrote:
> 
>> >>> On 11.04.18 at 13:53, <mingo@...nel.org> wrote:
>> > * Jan Beulich <JBeulich@...e.com> wrote:
>> > 
>> >> Additionally, x86 maintainers: is there a particular reason this (or
>> >> any functionally equivalent patch) isn't upstream yet? As indicated
>> >> before, I had not been able to find any discussion, and hence I
>> >> see no reason why this is a patch we effectively carry privately in
>> >> our distro branches (and likely other distros do so too).
>> > 
>> > The patch was merged 6 weeks ago and is now upstream:
>> > 
>> >   71c208dd54ab: x86/xen: Zero MSR_IA32_SPEC_CTRL before suspend
>> 
>> I'm sorry, but no, this isn't the patch I was inquiring about.
>> Instead I'm wondering of the disposition of the patch disabling
>> IBRS around a CPU going idle.
> 
> Got any specific link or subject line for that submission?

Sure, as written in the original response to Jürgen's patch:
https://patchwork.kernel.org/patch/10153843/

Jan