Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] KASLR: Do we have to worry about other arches than x86?
Date: Tue, 2 Jan 2018 21:06:11 +0200	[thread overview]
Message-ID: <D02628E8-9515-4914-BE44-5A6F66DD1264@gmail.com> (raw)
In-Reply-To: <CAA93jw5e9GG_dWDitpts+-e=v8r0m=mjT6SOKKBKwGv6b5=D=g@mail.gmail.com>

As I thought:

	https://lkml.org/lkml/2017/12/27/2

"AMD processors are not subject to the types of attacks that the kernel
page table isolation feature protects against.  The AMD microarchitecture
does not allow memory references, including speculative references, that
access higher privileged data when running in a lesser privileged mode
when that access would result in a page fault."

So it only affects *Intel* CPUs, though it's not yet clear to me how widespread the bug is in Intel-land.  Therefore ARM, PPC, etc are unaffected, and AMD might just get even more of a leg up in the server biz than previously anticipated.

Reading between the lines, I get the definite impression that this is a hardware exploit which uses *speculative* memory accesses to perform Rowhammer attacks in privileged memory areas.  So we probably shouldn't worry about it too much on consumer PCs or routers, even if they do use Intel x86 CPUs, except for the performance impact we might see where the mitigation is in place.  The performance impact would primarily affect system calls and context switches, I think, with much less impact on general computation.

 - Jonathan Morton


  parent reply	other threads:[~2018-01-02 19:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01 23:08 Dave Taht
     [not found] ` <CAJq5cE23bbiPE0a_9zd1VLnO7=c7bjmwwxVwaD2=to3fg5TOjA@mail.gmail.com>
2018-01-01 23:27   ` Jonathan Morton
2018-01-02 19:06 ` Jonathan Morton [this message]
2018-01-04 12:09   ` Jonathan Morton
2018-01-04 13:38     ` Dave Taht
2018-01-04 13:48       ` Jonathan Morton
2018-01-04 13:59         ` Dave Taht
2018-01-04 14:49           ` Jonathan Morton
2018-01-04 14:53             ` Dave Taht
2018-01-04 20:28               ` dpreed
2018-01-04 21:20                 ` Jonathan Morton
2018-01-04 21:40                 ` Dave Taht
2018-01-04 21:51                   ` valdis.kletnieks
2018-01-04 21:44     ` Joel Wirāmu Pauling
2018-01-04 21:47       ` Dave Taht
2018-01-04 21:52         ` Joel Wirāmu Pauling
2018-01-04 21:54           ` Dave Taht
2018-01-04 21:57             ` Joel Wirāmu Pauling
     [not found]           ` <1515103187.670416570@apps.rackspace.com>
2018-01-04 22:02             ` Joel Wirāmu Pauling
     [not found]       ` <1515103048.715224709@apps.rackspace.com>
2018-01-04 22:00         ` Joel Wirāmu Pauling
2018-01-04 22:09           ` dpreed
2018-01-04 22:13             ` Joel Wirāmu Pauling
2018-01-04 22:15             ` Dave Taht
2018-01-04 22:26             ` Jonathan Morton
2018-01-04 22:35               ` Joel Wirāmu Pauling
2018-01-04 22:58                 ` [Cerowrt-devel] Spectre and EBPF JIT dpreed
2018-01-05  4:53                   ` Dave Taht
2018-01-05 14:07                     ` Jonathan Morton
2018-01-05 15:35                       ` dpreed
2018-01-05 19:18                         ` Jonathan Morton
2018-01-05 20:15                           ` David Lang
2018-01-04 22:02 [Cerowrt-devel] KASLR: Do we have to worry about other arches than x86? dpreed
2018-01-04 22:02 dpreed
2018-01-04 22:04 ` Dave Taht
2018-01-04 22:12   ` dpreed

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D02628E8-9515-4914-BE44-5A6F66DD1264@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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