From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Dave Jones <davej@redhat.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
ksummit-2013-discuss@lists.linuxfoundation.org,
Kees Cook <keescook@chromium.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-2013-discuss] [ARM ATTEND] catching up on exploit mitigations
Date: Wed, 31 Jul 2013 10:40:12 +0100 [thread overview]
Message-ID: <20130731094012.GU24642@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130731000444.GC1281@redhat.com>
On Tue, Jul 30, 2013 at 08:04:44PM -0400, Dave Jones wrote:
> To use ARM as an example, the bugs I've seen have mostly been in arch specific
> code that does things like page-table manipulation. The chromebook bugs I
> was hitting for eg were various kinds of PTE corruption warnings.
Hmm, really? Did you reported these bugs? I'm not aware of mainline
having any changes related to bug reports on PTEs on ARM.
next prev parent reply other threads:[~2013-07-31 9:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 19:05 Kees Cook
2013-07-30 22:14 ` [Ksummit-2013-discuss] " Dave Jones
2013-07-30 22:28 ` H. Peter Anvin
2013-07-31 13:55 ` Jason Cooper
2013-07-30 23:11 ` Aaro Koskinen
2013-07-30 23:15 ` Dave Jones
2013-07-30 23:33 ` Kees Cook
2013-07-31 0:01 ` H. Peter Anvin
2013-07-30 23:58 ` Aaro Koskinen
2013-07-31 0:04 ` Dave Jones
2013-07-31 9:40 ` Russell King - ARM Linux [this message]
2013-07-31 14:24 ` Dave Jones
2013-08-01 2:47 ` Olof Johansson
2013-08-01 2:59 ` Dave Jones
2013-08-01 16:02 ` Vince Weaver
2013-08-21 15:26 ` Russell King - ARM Linux
2013-08-21 15:43 ` Dave Jones
2013-08-21 15:56 ` Russell King - ARM Linux
2013-08-01 9:13 ` Dan Carpenter
2013-08-01 19:05 ` Dave Jones
2013-08-01 19:16 ` Dan Carpenter
2013-08-01 19:26 ` Julia Lawall
2013-08-13 4:51 ` Laura Abbott
2013-08-26 19:56 ` Mark Brown
2013-08-27 2:09 ` Laura Abbott
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=20130731094012.GU24642@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=aaro.koskinen@iki.fi \
--cc=davej@redhat.com \
--cc=keescook@chromium.org \
--cc=ksummit-2013-discuss@lists.linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®