From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Kees Cook <keescook@chromium.org>,
Oleg Nesterov <oleg@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Florian Weimer <fweimer@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] powerpc: Do not make the entire heap executable
Date: Mon, 22 Aug 2016 13:22:56 -0600 [thread overview]
Message-ID: <20160822192256.GA10199@obsidianresearch.com> (raw)
In-Reply-To: <47a2e87e-5299-a009-8a65-5171b33967a1@redhat.com>
On Mon, Aug 22, 2016 at 08:37:05PM +0200, Denys Vlasenko wrote:
> >Is this going to break any application ? I am asking because you
> >mentioned the patch is lightly tested.
>
> I booted powerpc64 machine with RHEL7 installation,
> it did not catch fire.
When I authored the original patch my concern was if it had unforseen
impacts on other platforms. I know PPC32 and ARM32 work OK.
It would good to test other platforms as well.
Jason
--
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>
prev parent reply other threads:[~2016-08-22 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 13:00 [PATCH v4] powerpc: Do not make the entire heap executable Denys Vlasenko
2016-08-10 13:36 ` Oleg Nesterov
2016-08-19 12:33 ` Denys Vlasenko
2016-08-21 15:47 ` Aneesh Kumar K.V
2016-08-22 18:37 ` Denys Vlasenko
2016-08-22 19:22 ` Jason Gunthorpe [this message]
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=20160822192256.GA10199@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=dvlasenk@redhat.com \
--cc=fweimer@redhat.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 \
/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;
as well as URLs for NNTP newsgroup(s).