tags 441387 fixed-upstream
thanks
Hello François,
> The mprotect manpage specifies that:
>
> "Whether PROT_EXEC has any effect different from PROT_READ is
> architecture and kernel version dependent."
>
> which is true, but it should also specify that whether PROT_WRITE
> implies PROT_READ is architecture dependant and that it is the case on
> x86 platforms.
Yes, agreed. I added a sentence:
Whether PROT_EXEC has any effect different from PROT_READ is
architecture and kernel version dependent. On some hardware
architectures (e.g., x86), PROT_WRITE implies PROT_READ.
> The same holds true for the mmap manpage.
I also added a similar sentence to mmap(2).
> However, what
> makes this manpage especially misleading in that regard is that it
> states that:
>
> "For example, if the memory had previously been marked PROT_READ, and
> mprotect() is then called with prot PROT_WRITE, it will no longer be
> readable."
>
> which, as I said, is not true on x86 platforms. I think would be better
> to reverse this sentence so as to say:
>
> "For example, if the memory had previously been marked PROT_WRITE, and
> mprotect() is then called with prot PROT_READ, it will no longer be
> writable."
I cannot find this text in the upstream man page (is it in mmap.2
or mprotect.2?). Is this some text added by Debian?
Cheers,
Michael
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance? Grab the latest tarball at
http://www.kernel.org/pub/linux/docs/manpages/
read the HOWTOHELP file and grep the source files for 'FIXME'.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
