mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Jeremy Linton <jeremy.linton@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: mlangsdo@redhat.com, suzuki.poulose@arm.com,
	marc.zyngier@arm.com, catalin.marinas@arm.com,
	julien.thierry@arm.com, will.deacon@arm.com,
	linux-kernel@vger.kernel.org, Andre.Przywara@arm.com,
	Dave.Martin@arm.com, shankerd@codeaurora.org
Subject: Re: [v8 09/10] arm64: add sysfs vulnerability show for speculative store bypass
Date: Thu, 25 Apr 2019 19:11:11 +0200 (CEST)	[thread overview]
Message-ID: <1375455768.808427.1556212271639@email.ionos.de> (raw)
In-Reply-To: <20190415212129.1112-10-jeremy.linton@arm.com>


> Jeremy Linton <jeremy.linton@arm.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@arm.com>

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

on a Raspberry Pi 3 B

  reply	other threads:[~2019-04-25 17:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 21:21 [v8 00/10] arm64: add system vulnerability sysfs entries Jeremy Linton
2019-04-15 21:21 ` [v8 01/10] arm64: Provide a command line to disable spectre_v2 mitigation Jeremy Linton
2019-04-15 21:21 ` [v8 02/10] arm64: add sysfs vulnerability show for spectre v1 Jeremy Linton
2019-04-15 21:21 ` [v8 03/10] arm64: add sysfs vulnerability show for meltdown Jeremy Linton
2019-04-15 21:21 ` [v8 04/10] arm64: Advertise mitigation of Spectre-v2, or lack thereof Jeremy Linton
2019-04-15 21:21 ` [v8 05/10] arm64: Use firmware to detect CPUs that are not affected by Spectre-v2 Jeremy Linton
2019-04-15 21:21 ` [v8 06/10] arm64: Always enable spectrev2 vulnerability detection Jeremy Linton
2019-04-15 21:21 ` [v8 07/10] arm64: add sysfs vulnerability show for spectre v2 Jeremy Linton
2019-04-15 21:21 ` [v8 08/10] arm64: Always enable ssb vulnerability detection Jeremy Linton
2019-04-15 21:21 ` [v8 09/10] arm64: add sysfs vulnerability show for speculative store bypass Jeremy Linton
2019-04-25 17:11   ` Stefan Wahren [this message]
2019-04-15 21:21 ` [v8 10/10] arm64: enable generic CPU vulnerabilites support Jeremy Linton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1375455768.808427.1556212271639@email.ionos.de \
    --to=stefan.wahren@i2se.com \
    --cc=Andre.Przywara@arm.com \
    --cc=Dave.Martin@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=jeremy.linton@arm.com \
    --cc=julien.thierry@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mlangsdo@redhat.com \
    --cc=shankerd@codeaurora.org \
    --cc=suzuki.poulose@arm.com \
    --cc=will.deacon@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®