From: "H. Peter Anvin" <hpa@zytor.com>
To: Kees Cook <keescook@chromium.org>, LKML <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org
Subject: Re: [RFC] stack and heap are executable on x86_64
Date: Thu, 20 Dec 2012 19:30:07 -0800 [thread overview]
Message-ID: <2069d03f-0dea-4432-b9aa-5095bafd07d6@email.android.com> (raw)
In-Reply-To: <CAGXu5jJtoPdhZ_DGeaCT1AsUuLfS4LThaR0PkKbwmTG2rDPZKw@mail.gmail.com>
Wtf...
Kees Cook <keescook@chromium.org> wrote:
>On Thu, Dec 20, 2012 at 7:00 PM, Kees Cook <keescook@chromium.org>
>wrote:
>> While trying to fix test_nx, I discovered that it looks like stack
>and
>> heap are executable again (at least on x86_64). :( I tried to bisect
>
>Btw, this ends up looking like this on v3.4:
>
>[ 2.486223] test_nx: Testing NX protection ...
>[ 2.487468] test_nx: calling ffff88001dd57e45 (0xC3)
>[ 2.488766] test_nx: stack is executable
>[ 2.489802] test_nx: calling ffff88001e2c7580 (0xC3)
>[ 2.491106] test_nx: heap is executable
>[ 2.492086] test_nx: calling ffffffff81803c80 (0xC3)
>[ 2.493201] test_nx: calling ffffffffa0002220 (0xC3)
>[ 2.493843] test_nx: calling ffffffffa0001224 (0xC3)
>[ 2.494549] test_nx: Done testing.
>
>-Kees
>
>--
>Kees Cook
>Chrome OS Security
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
next prev parent reply other threads:[~2012-12-21 3:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 3:00 Kees Cook
2012-12-21 3:06 ` Kees Cook
2012-12-21 3:30 ` H. Peter Anvin [this message]
2012-12-21 4:44 ` H. Peter Anvin
2012-12-21 6:27 ` Yinghai Lu
2012-12-21 17:01 ` H. Peter Anvin
2012-12-21 17:28 ` Yinghai Lu
2012-12-21 17:36 ` H. Peter Anvin
2012-12-21 21:26 ` Yinghai Lu
2012-12-21 22:22 ` Yinghai Lu
2012-12-21 22:23 ` H. Peter Anvin
2012-12-21 22:26 ` Yinghai Lu
2012-12-21 22:28 ` H. Peter Anvin
2012-12-21 22:30 ` Yinghai Lu
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=2069d03f-0dea-4432-b9aa-5095bafd07d6@email.android.com \
--to=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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®