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] [day] [month] [year] [list]
Message-ID: <a924b8f8-7f34-0144-74d1-4d2ba09341dc@redhat.com>
Date:   Fri, 15 Nov 2019 09:40:56 -0500
From:   Waiman Long <longman@...hat.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org, Josh Poimboeuf <jpoimboe@...hat.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Mark Gross <mgross@...ux.intel.com>,
        Tony Luck <tony.luck@...el.com>
Subject: Re: [PATCH] x86/speculation: Fix incorrect MDS/TAA mitigation status

On 11/14/19 5:09 PM, Borislav Petkov wrote:
> On Thu, Nov 14, 2019 at 04:58:24PM -0500, Waiman Long wrote:
>>> Maybe delay MDS mitigation print till TAA is evaluated.
>> I will see what can be done about that. However, this is not a critical
>> issue and I may not change it if there is no easy solution.
> Swapping the two mitigation selection calls in check_bugs() might
> work...

Not really. If taa_select_mitigation() goes first and with
"tsx_async_abort=off" only, the mds file is correct, but the taa file
will be wrong.

Cheers,
Longman

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ