public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Meltdown and Spectre in CIP
Date: Thu, 15 Feb 2018 11:44:51 +0000	[thread overview]
Message-ID: <1518695091.3422.24.camel@codethink.co.uk> (raw)
In-Reply-To: <TY1PR06MB07021E0DE8BDB329DFC8A32FB7EA0@TY1PR06MB0702.apcprd06.prod.outlook.com>

On Tue, 2018-01-16 at 08:01 +0000, Chris Paterson wrote:
[...]
> > Meltdown:
> > - arm 32-bit: Not affected???(ARM reports that only the Cortex-A75 is
> > ? affected, but I haven't seen information from other architecture
> > ? licensees.)
> 
> ARM also lists that meltdown subvariant '3a' affects some arm 32-bit
> processors [1], but say that "In general, it is not believed that
> software mitigations for this issue are necessary".
> 
> The whitepaper ARM link to [2] implies that ARM don't think this is
> an issue worth worrying about as the information that can be obtained
> from the system registers is "not material".
> 
> Have you heard/seen anything to contradict this statement?

No I haven't.

[...]
> Will you be keeping an eye on Spectre patches on behalf of CIP as
> part of your maintainer role? I guess you may be in the loop a bit
> more than the rest of us?

I will look at the mitigations as they land upstream, but I still think
these are low priority security issues for CIP.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

  reply	other threads:[~2018-02-15 11:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 14:16 [cip-dev] Meltdown and Spectre in CIP Ben Hutchings
2018-01-16  8:01 ` Chris Paterson
2018-02-15 11:44   ` Ben Hutchings [this message]
2018-03-02 17:52     ` Jan Kiszka
2018-03-08 22:45 ` Ben Hutchings

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=1518695091.3422.24.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox