From: Andrew Morton <akpm@linux-foundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: "Kees Cook" <keescook@chromium.org>,
linux-kernel@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, "Alexander Viro" <viro@zeniv.linux.org.uk>,
"Ismael Ripoll" <iripoll@upv.es>,
"Hector Marco-Gisbert" <hecmargi@upv.es>,
"Jan-Simon Möller" <dl9pf@gmx.de>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] ASLR: fix stack randomization on 64-bit systems
Date: Wed, 18 Feb 2015 12:11:38 -0800 [thread overview]
Message-ID: <20150218121138.b977e1aba69d8e3e2fb2cbc1@linux-foundation.org> (raw)
In-Reply-To: <20150218091543.GF3211@pd.tnic>
On Wed, 18 Feb 2015 10:15:43 +0100 Borislav Petkov <bp@alien8.de> wrote:
> > CVE-2015-1593
> >
> > Signed-off-by: Hector Marco-Gisbert <hecmargi@upv.es>
> > Signed-off-by: Ismael Ripoll <iripoll@upv.es>
> > [kees: rebase, fix 80 char, clean up commit message, add test example, cve]
> > Signed-off-by: Kees Cook <keescook@chromium.org>
> > Cc: stable@vger.kernel.org
>
> Ok, I'm picking this up. Do scream if someone else wants to do that,
I grabbed it, but shall drop my copy if it turns up in linux-next.
> otherwise it is going to tip next week, after the merge window is over.
It's tagged for -stable backporting, so it should go into 3.20?
next prev parent reply other threads:[~2015-02-18 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 17:33 Kees Cook
2015-02-16 20:49 ` Andy Lutomirski
2015-02-18 3:27 ` Kees Cook
2015-02-18 9:15 ` Borislav Petkov
2015-02-18 20:11 ` Andrew Morton [this message]
2015-02-18 20:19 ` Ingo Molnar
2015-02-18 20:25 ` Borislav Petkov
2015-02-18 20:26 ` Ingo Molnar
2015-02-19 19:27 ` [tip:x86/urgent] x86, mm/ASLR: Fix " tip-bot for Hector Marco-Gisbert
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=20150218121138.b977e1aba69d8e3e2fb2cbc1@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dl9pf@gmx.de \
--cc=hecmargi@upv.es \
--cc=hpa@zytor.com \
--cc=iripoll@upv.es \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--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
Powered by JetHome