From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: linux-omap@vger.kernel.org,
arm-soc <linux-arm-kernel@lists.infradead.org>
Subject: Re: Spectre and Cortex-A8/A9
Date: Thu, 10 May 2018 07:47:03 -0700 [thread overview]
Message-ID: <20180510144703.GD98604@atomide.com> (raw)
In-Reply-To: <CAHCN7x+ghEW__YwgbXYO4g9HNKkwkQtXiswL1jihj0wwfKuR4Q@mail.gmail.com>
* Adam Ford <aford173@gmail.com> [180509 18:23]:
> There is a lot of information pushed around the web about the Spectre
> bug. I went to ARM's support site and there are some patches
> available from February that haven't made their way into the mainline.
>
> Sorry if this has been covered before, but I am curious to know if
> there is a good place or method to determine whether or not the
> Cortex-A8 and A9 are still vulnerable and which versions or 4.4, 4.9,
> or 4.14 have any items fixed.
Well while we're waiting to figure out what all needs to be fixed,
here's what I'd do meanwhile:
1. Make sure the bootloader sets IBE bit
2. Make sure you have CONFIG_ARM_ERRATA_430973=y
3. Apply Marc Zyngier's patches from thread "[PATCH v4 0/6] 32bit ARM
branch predictor hardening", but note that these are still being
discussed
4. Update kernel when patches that have been validated against
test cases get merged
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Spectre and Cortex-A8/A9
Date: Thu, 10 May 2018 07:47:03 -0700 [thread overview]
Message-ID: <20180510144703.GD98604@atomide.com> (raw)
In-Reply-To: <CAHCN7x+ghEW__YwgbXYO4g9HNKkwkQtXiswL1jihj0wwfKuR4Q@mail.gmail.com>
* Adam Ford <aford173@gmail.com> [180509 18:23]:
> There is a lot of information pushed around the web about the Spectre
> bug. I went to ARM's support site and there are some patches
> available from February that haven't made their way into the mainline.
>
> Sorry if this has been covered before, but I am curious to know if
> there is a good place or method to determine whether or not the
> Cortex-A8 and A9 are still vulnerable and which versions or 4.4, 4.9,
> or 4.14 have any items fixed.
Well while we're waiting to figure out what all needs to be fixed,
here's what I'd do meanwhile:
1. Make sure the bootloader sets IBE bit
2. Make sure you have CONFIG_ARM_ERRATA_430973=y
3. Apply Marc Zyngier's patches from thread "[PATCH v4 0/6] 32bit ARM
branch predictor hardening", but note that these are still being
discussed
4. Update kernel when patches that have been validated against
test cases get merged
Regards,
Tony
next prev parent reply other threads:[~2018-05-10 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 18:21 Spectre and Cortex-A8/A9 Adam Ford
2018-05-09 18:21 ` Adam Ford
2018-05-10 14:47 ` Tony Lindgren [this message]
2018-05-10 14:47 ` Tony Lindgren
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=20180510144703.GD98604@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.