All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot, cache speculation side channel attacks and ARM
Date: Fri, 19 Jan 2018 16:56:14 -0500	[thread overview]
Message-ID: <20180119215614.GZ4660@bill-the-cat> (raw)

Hey all,

So, now that things have quieted down a little bit in this area, I've
been wondering about something.  Over on the U-Boot side of things, are
there changes we need to make in order to support the kernel side of the
various mitigations properly?  I know that for example currently
https://developer.arm.com/support/security-update talks about ATF
patches, in the context of AArch64 however.  But on the other hand for
variant 2, there's nothing listed on the Linux side for 32bit ARM, but
there is for non-Linux OSes.

And, in the event I'm also missing something else entirely that we need
to do here, is there something that we need to be doing?  Or is it still
too early at this point in time to know?

Thanks all!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180119/265738b6/attachment.sig>

             reply	other threads:[~2018-01-19 21:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 21:56 Tom Rini [this message]
2018-01-19 22:21 ` [U-Boot] U-Boot, cache speculation side channel attacks and ARM Mark Kettenis
2018-01-19 23:10   ` Nishanth Menon
2018-01-20  9:47     ` Michael Nazzareno Trimarchi
2018-01-20 10:45     ` Marc Zyngier
2018-01-20 10:51   ` Marc Zyngier
2018-01-20 10:42 ` Marc Zyngier
2018-01-20 10:45   ` Michael Nazzareno Trimarchi
2018-01-20 11:31     ` Marc Zyngier
2018-01-20 12:13       ` Michael Nazzareno Trimarchi
2018-01-20 12:29       ` Russell King
2018-01-20 12:45         ` Marc Zyngier

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=20180119215614.GZ4660@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.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.