From: Roland McGrath <mcgrathr@google.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Will Drewry <wad@chromium.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Al Viro <viro@zeniv.linux.org.uk>, Eric Paris <eparis@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Rik van Riel <riel@redhat.com>, Nitin Gupta <ngupta@vflare.org>,
Hugh Dickins <hughd@google.com>,
Shaohua Li <shaohua.li@intel.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] mmap: add sysctl for controlling ~VM_MAYEXEC taint
Date: Tue, 16 Aug 2011 12:46:17 -0700 [thread overview]
Message-ID: <CAB=4xhrStO=ec92KD2W6V3QzjgaET5jvF1PXdAdu_LdFg7G82Q@mail.gmail.com> (raw)
In-Reply-To: <20110816194050.GB4484@csn.ul.ie>
On Tue, Aug 16, 2011 at 12:40 PM, Mel Gorman <mel@csn.ul.ie> wrote:
> They might result in the same system call but one of them creates
> the file under /dev/shm which should not have the same permissions
> problem. The library really appears to want to create a shared
> executable object, using shm_open does not appear that unreasonable
> to me.
People do use shm_open. Some systems mount /dev/shm with noexec.
That's why we're here in the first place.
> Which then needs to be copied in each distro wanting to do the same
> thing and is not backwards compatible where as using shm_open is.
Each distro wanting to set noexec on its /dev/shm mounts has to set the
sysctl (or its default in their kernel builds), yes. Otherwise they are
not compatible with the expectation of using PROT_EXEC on files opened with
shm_open.
Thanks,
Roland
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-16 19:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 20:57 Will Drewry
2011-08-16 9:33 ` Mel Gorman
2011-08-16 17:07 ` Roland McGrath
2011-08-16 19:40 ` Mel Gorman
2011-08-16 19:46 ` Roland McGrath [this message]
2011-08-16 19:50 ` Will Drewry
2011-08-16 19:50 ` Will Drewry
2011-08-17 23:22 ` Valdis.Kletnieks
2011-08-16 21:54 ` Andrew Morton
2011-08-16 22:35 ` Will Drewry
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='CAB=4xhrStO=ec92KD2W6V3QzjgaET5jvF1PXdAdu_LdFg7G82Q@mail.gmail.com' \
--to=mcgrathr@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=ngupta@vflare.org \
--cc=riel@redhat.com \
--cc=shaohua.li@intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wad@chromium.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