From: Andrew Morton <akpm@linux-foundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Ben Hutchings <ben@decadent.org.uk>,
Luis Henriques <luis.henriques@canonical.com>,
LKML <linux-kernel@vger.kernel.org>,
Julien Tinnes <jln@google.com>, PaX Team <pageexec@freemail.hu>,
Emese Revfy <re.emese@gmail.com>
Subject: Re: + signal-always-clear-sa_restorer-on-execve.patch added to -mm tree
Date: Mon, 11 Mar 2013 14:42:34 -0700 [thread overview]
Message-ID: <20130311144234.88e2f35792a5157f9fb45c64@linux-foundation.org> (raw)
In-Reply-To: <CAGXu5jLxwKUT6hYij-u1BP3kPqq-h3p-JKUaGK_J8WWhOvYVsQ@mail.gmail.com>
On Mon, 11 Mar 2013 14:33:18 -0700 Kees Cook <keescook@chromium.org> wrote:
> > patch #1: use SA_RESTORER, cc stable (please promise me this will work OK)
>
> I don't have the ability to build all the architectures, but it seems
> like the best flag based on code review.
SA_RESTORER looks OK back to 3.5 (at least).
> > patch #2: switch to __ARCH_HAS_SA_RESTORER, no cc stable
> >
> > I'm assuming this is all for 3.10, btw. If you think it should be in
> > 3.9 then you need to write scarier changelogs.
>
> Well, I'm not sure it needs to be scarier; it's a serious local ASLR
> info leak. I was hoping it could go into 3.9 since the expectation is
> for it to go to stable, so why not put it in 3.9 now?
OK.
> Do you want me to spin up the 2-patch solution or is it too much of a hack?
Is OK, I have it all lined up.
next prev parent reply other threads:[~2013-03-11 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130311202255.942745A4121@corp2gmr1-2.hot.corp.google.com>
2013-03-11 20:37 ` Kees Cook
2013-03-11 21:01 ` Andrew Morton
2013-03-11 21:03 ` Kees Cook
2013-03-11 21:22 ` Andrew Morton
2013-03-11 21:33 ` Kees Cook
2013-03-11 21:42 ` Andrew Morton [this message]
2013-03-11 21:20 ` Greg KH
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=20130311144234.88e2f35792a5157f9fb45c64@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jln@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--cc=pageexec@freemail.hu \
--cc=re.emese@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
all inboxes | Powered by JetHome®