On 6/28/06, Pavel Machek <[email protected]> wrote:
mmap() behaviour always was platform-specific, and it happens to be quite strange on i386. So what.
Nonsense. The mmap semantics is specified in POSIX. If something doesn't work as requested it is a bug. For the specific issue hurting x86 and likely others the standard explicitly allows requiring PROT_READ to be used or implicitly adding it. Don't confuse people with wrong statement like yours. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: make PROT_WRITE imply PROT_READ
- From: Pavel Machek <[email protected]>
- Re: make PROT_WRITE imply PROT_READ
- References:
- Re: make PROT_WRITE imply PROT_READ
- From: Robert Hancock <[email protected]>
- Re: make PROT_WRITE imply PROT_READ
- From: Jason Baron <[email protected]>
- Re: make PROT_WRITE imply PROT_READ
- From: Arjan van de Ven <[email protected]>
- Re: make PROT_WRITE imply PROT_READ
- From: Jason Baron <[email protected]>
- Re: make PROT_WRITE imply PROT_READ
- From: Arjan van de Ven <[email protected]>
- Re: make PROT_WRITE imply PROT_READ
- From: "Ulrich Drepper" <[email protected]>
- Re: make PROT_WRITE imply PROT_READ
- From: Pavel Machek <[email protected]>
- Re: make PROT_WRITE imply PROT_READ
- From: "Ulrich Drepper" <[email protected]>
- Re: make PROT_WRITE imply PROT_READ
- From: Pavel Machek <[email protected]>
- Re: make PROT_WRITE imply PROT_READ
- Prev by Date: Re: [klibc] klibc and what's the next step?
- Next by Date: [PATCH 3/3] SELinux: Update USB code with new kill_proc_info_as_uid
- Previous by thread: Re: make PROT_WRITE imply PROT_READ
- Next by thread: Re: make PROT_WRITE imply PROT_READ
- Index(es):
 |