From: Ralf Baechle <ralf@linux-mips.org>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-mips@linux-mips.org, libc-alpha@sourceware.org
Subject: Impact of removing VM_EXEC from brk area
Date: Thu, 13 Nov 2014 13:24:06 +0100 [thread overview]
Message-ID: <20141113122406.GA19763@linux-mips.org> (raw)
A patch to remove VM_EXEC from VM_DATA_DEFAULT_FLAGS for MIPS has been
submitted to me with the primary motivation for this change being
some performance improvment. In other words, the patch would remove
execute permission from a process brk area. It's however unclear to
me how much software wreckage would result from such a change, even
if the execute permission for the stack area remains unchanged.
So, what would break?
Thanks,
Ralf
--
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>
reply other threads:[~2014-11-13 12:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141113122406.GA19763@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mm@kvack.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).