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]
Date:   Thu, 25 Apr 2019 19:11:11 +0200 (CEST)
From:   Stefan Wahren <stefan.wahren@...e.com>
To:     Jeremy Linton <jeremy.linton@....com>,
        linux-arm-kernel@...ts.infradead.org
Cc:     mlangsdo@...hat.com, suzuki.poulose@....com, marc.zyngier@....com,
        catalin.marinas@....com, julien.thierry@....com,
        will.deacon@....com, linux-kernel@...r.kernel.org,
        Andre.Przywara@....com, Dave.Martin@....com,
        shankerd@...eaurora.org
Subject: Re: [v8 09/10] arm64: add sysfs vulnerability show for speculative
 store bypass


> Jeremy Linton <jeremy.linton@....com> hat am 15. April 2019 um 23:21 geschrieben:
> 
> 
> Return status based on ssbd_state and __ssb_safe. If the
> mitigation is disabled, or the firmware isn't responding then
> return the expected machine state based on a whitelist of known
> good cores.
> 
> Given a heterogeneous machine, the overall machine vulnerability
> defaults to safe but is reset to unsafe when we miss the whitelist
> and the firmware doesn't explicitly tell us the core is safe.
> In order to make that work we delay transitioning to vulnerable
> until we know the firmware isn't responding to avoid a case
> where we miss the whitelist, but the firmware goes ahead and
> reports the core is not vulnerable. If all the cores in the
> machine have SSBS, then __ssb_safe will remain true.
> 
> Signed-off-by: Jeremy Linton <jeremy.linton@....com>

Tested-by: Stefan Wahren <stefan.wahren@...e.com>

on a Raspberry Pi 3 B

Powered by blists - more mailing lists