All of lore.kernel.org
 help / color / mirror / Atom feed
From: nobuhiro1.iwamatsu@toshiba.co.jp (nobuhiro1.iwamatsu at toshiba.co.jp)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] MDS and other speculation issues
Date: Thu, 16 May 2019 00:44:11 +0000	[thread overview]
Message-ID: <TYAPR01MB41891550E349BF4F04888203920A0@TYAPR01MB4189.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <1557920010.3952.2.camel@codethink.co.uk>

Hi Ben,

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Ben
> Hutchings
> Sent: Wednesday, May 15, 2019 8:34 PM
> To: cip-dev at lists.cip-project.org
> Subject: [cip-dev] MDS and other speculation issues
> 
> 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.

Thank you for your work and information.
I'm just looking into a test tool for this issue, but please let me know what
you already know.

There is a spectre-meltdown-checker, but we can not do a detailed test with this.
https://github.com/speed47/spectre-meltdown-checker/

> 
> Ben.
> 
Best regards,
  Nobuhirio

  reply	other threads:[~2019-05-16  0:44 UTC|newest]

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