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: <YxxCMSYaI/o3QH03@nazgul.tnic>
Date:   Sat, 10 Sep 2022 09:52:27 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Manikandan Jagatheesan <mjagatheesan@...are.com>
Cc:     "peterz@...radead.org" <peterz@...radead.org>,
        "jpoimboe@...nel.org" <jpoimboe@...nel.org>,
        "tglx@...utronix.de" <tglx@...utronix.de>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
        "x86@...nel.org" <x86@...nel.org>, "hpa@...or.com" <hpa@...or.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "srivatsa@...il.mit.edu" <srivatsa@...il.mit.edu>,
        Peter Jonasson <pjonasson@...are.com>,
        Yiu Cho Lau <lauyiuch@...are.com>,
        Rajender M <manir@...are.com>,
        Abdul Anshad Azeez <aazees@...are.com>,
        Kodeswaran Kumarasamy <kkumarasamy@...are.com>,
        Rahul Gopakumar <gopakumarr@...are.com>
Subject: Re: Performance Regression in Linux Kernel 5.19

On Fri, Sep 09, 2022 at 11:46:08AM +0000, Manikandan Jagatheesan wrote:
> After performing the bisect between kernel 5.18 and 5.19, we 
> identified the root cause to be the enablement of IBRS mitigation 
> for spectre_v2 vulnerability by commit 6ad0ad2bf8a6 ("x86/bugs: 
> Report Intel retbleed vulnerability").

What I'm wondering about is why does the guest enable IBRS when booting
on your HV?

I'm guessing you're exposing SPEC_CTRL and all the feature flags so that
the detection in spectre_v2_select_mitigation(), the SPECTRE_V2_CMD_AUTO
case, hits.

But then, why are you emulating a CPU which is vulnerable to retbleed?

Because as far as the guest is concerned, filling the RSB on VMEXIT
should be good enough and the guest doesn't have to do anything else.

IOW, X86_BUG_RETBLEED should not be set on the guest booting on your HV.

Hmmm?

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ