All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] MDS and other speculation issues
Date: Wed, 15 May 2019 12:33:30 +0100	[thread overview]
Message-ID: <1557920010.3952.2.camel@codethink.co.uk> (raw)

As with the earlier speculation vulnerabilities, I don't believe that
MDS should be a particularly severe issue for CIP-based systems.

Nevertheless, I have prepared a backport of the mitigations for MDS
(and some changes to the mitigations for other speculation issues) for 
4.4.  This was included in 4.4.180-rc1, which is out for review now.  I
did not have the chance to test this thoroughly, so review and testing
are needed.

Ben.

-- 
Ben Hutchings, Software Developer                ?        Codethink Ltd
https://www.codethink.co.uk/                 Dale House, 35 Dale Street
                                     Manchester, M1 2HF, United Kingdom

             reply	other threads:[~2019-05-15 11:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15 11:33 Ben Hutchings [this message]
2019-05-16  0:44 ` [cip-dev] MDS and other speculation issues nobuhiro1.iwamatsu at toshiba.co.jp
2019-05-16 16:29   ` 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=1557920010.3952.2.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 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.