From: Florian Weimer <fw@deneb.enyo.de>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Florian Weimer <fweimer@redhat.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
Kees Cook <keescook@chromium.org>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Paul Mackerras <paulus@samba.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH v5] powerpc: Do not make the entire heap executable
Date: Wed, 28 Sep 2016 15:12:57 +0200 [thread overview]
Message-ID: <87k2dwgobq.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20160928025544.GA24199@obsidianresearch.com> (Jason Gunthorpe's message of "Tue, 27 Sep 2016 20:55:44 -0600")
* Jason Gunthorpe:
> Eg that 32 bit powerpc currently unconditionally injects writable,
> executable pages into a user space process.
>
> This critically undermines all the W^X security work that has been
> done in the tool chain and user space by the PPC community.
Exactly, this is how we found it. I have pretty extensive execmod
tests, and I'm going to put them into glibc eventually. It would be
nice to cut down the number of architectures where it will fail.
(Even if you don't believe in security hardening.)
WARNING: multiple messages have this Message-ID (diff)
From: Florian Weimer <fw@deneb.enyo.de>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Florian Weimer <fweimer@redhat.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
Kees Cook <keescook@chromium.org>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Paul Mackerras <paulus@samba.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH v5] powerpc: Do not make the entire heap executable
Date: Wed, 28 Sep 2016 15:12:57 +0200 [thread overview]
Message-ID: <87k2dwgobq.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20160928025544.GA24199@obsidianresearch.com> (Jason Gunthorpe's message of "Tue, 27 Sep 2016 20:55:44 -0600")
* Jason Gunthorpe:
> Eg that 32 bit powerpc currently unconditionally injects writable,
> executable pages into a user space process.
>
> This critically undermines all the W^X security work that has been
> done in the tool chain and user space by the PPC community.
Exactly, this is how we found it. I have pretty extensive execmod
tests, and I'm going to put them into glibc eventually. It would be
nice to cut down the number of architectures where it will fail.
(Even if you don't believe in security hardening.)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-09-28 13:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 18:51 [PATCH v5] powerpc: Do not make the entire heap executable Denys Vlasenko
2016-08-22 18:51 ` Denys Vlasenko
2016-09-28 1:42 ` Michael Ellerman
2016-09-28 1:42 ` Michael Ellerman
2016-09-28 2:55 ` Jason Gunthorpe
2016-09-28 2:55 ` Jason Gunthorpe
2016-09-28 13:12 ` Florian Weimer [this message]
2016-09-28 13:12 ` Florian Weimer
2016-09-28 17:16 ` Kees Cook
2016-09-28 17:16 ` Kees Cook
2016-09-29 16:07 ` Oleg Nesterov
2016-09-29 16:07 ` Oleg Nesterov
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=87k2dwgobq.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dvlasenk@redhat.com \
--cc=fweimer@redhat.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oleg@redhat.com \
--cc=paulus@samba.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.