All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: Starting to go public?
Date: Tue, 5 Mar 2019 21:36:57 +0100 (CET)	[thread overview]
Message-ID: <nycvar.YFH.7.76.1903052133170.19912@cbobk.fhfr.pm> (raw)
In-Reply-To: <afbbc196-dd45-fca0-4553-24bb2090b3f1@citrix.com>

On Tue, 5 Mar 2019, speck for Andrew Cooper wrote:

> > Looks like the papers are starting to leak:
> >
> >    https://arxiv.org/pdf/1903.00446.pdf
> >
> > yes, yes, a lot of the attack seems to be about rowhammer, but the
> > "spolier" part looks like MDS.
> 
> So Intel was aware of that paper, but wasn't expecting it to go public
> today.
> 
> =46rom their point of view, it is a traditional timing sidechannel on a
> piece of the pipeline (which happens to be component which exists for
> speculative memory disambiguation).
> 
> There are no proposed changes to the MDS timeline at this point.

So this is not the paper that caused the panic fearing that PSF might leak 
earlier than the rest of the issues in mid-february (which few days later 
Intel claimed to have succesfully negotiated with the researches not to 
publish before the CRD)?

Thanks,

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2019-03-05 20:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05 16:43 [MODERATED] Starting to go public? Linus Torvalds
2019-03-05 17:02 ` [MODERATED] " Andrew Cooper
2019-03-05 20:36   ` Jiri Kosina [this message]
2019-03-05 22:31     ` Andrew Cooper
2019-03-06 16:18       ` [MODERATED] Encrypted Message Jon Masters
2019-03-05 17:10 ` Jon Masters

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=nycvar.YFH.7.76.1903052133170.19912@cbobk.fhfr.pm \
    --to=jkosina@suse.com \
    --cc=speck@linutronix.de \
    /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.