linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Seaborn <mseaborn-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] mprotect(2): mention effect of READ_IMPLIES_EXEC personality flag
Date: Fri, 23 Apr 2010 17:31:01 +0100	[thread overview]
Message-ID: <w2ke1cf9ca11004230931yff731f6gb45134c3d0d51cbe@mail.gmail.com> (raw)

I puzzled over mprotect()'s effect on /proc/*/maps for a while
yesterday -- it was setting "x" without PROT_EXEC being specified.
Here is a patch to add some explanation.

mprotect(2): mention effect of READ_IMPLIES_EXEC personality flag

diff --git a/man2/mprotect.2 b/man2/mprotect.2
index d7b9712..a5aa2fb 100644
--- a/man2/mprotect.2
+++ b/man2/mprotect.2
@@ -125,7 +125,15 @@ Whether
 .B PROT_EXEC
 has any effect different from
 .B PROT_READ
-is architecture- and kernel version-dependent.
+depends on processor architecture, kernel version, and process state. If
+.B READ_IMPLIES_EXEC
+is set in the process's personality flags (see
+.BR personality (2)),
+specifying
+.B PROT_READ
+will implicitly add
+.BR PROT_EXEC.
+
 On some hardware architectures (e.g., i386),
 .B PROT_WRITE
 implies
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2010-04-23 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 16:31 Mark Seaborn [this message]
     [not found] ` <w2ke1cf9ca11004230931yff731f6gb45134c3d0d51cbe-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-05 11:28   ` [PATCH] mprotect(2): mention effect of READ_IMPLIES_EXEC personality flag Michael Kerrisk (man-pages)
     [not found]     ` <54D353CB.9050401-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-07  2:02       ` Mark Seaborn
     [not found]         ` <CAL82V5M701JvwLnURQkO=anrAu8pp=bOZRZbCKN_umg7VxVdUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-08  8:08           ` Michael Kerrisk (man-pages)
2015-02-05 13:18   ` Michael Kerrisk (man-pages)

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=w2ke1cf9ca11004230931yff731f6gb45134c3d0d51cbe@mail.gmail.com \
    --to=mseaborn-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).