On 6/29/06, Pavel Machek <[email protected]> wrote:
Can you quote part of POSIX where it says that PROT_WRITE must imply PROT_READ?
I never wrote that. What POSIX does specify is that PROT_READ can optionally be implicitly set. - 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/
- References:
- Re: make PROT_WRITE imply PROT_READ
- From: Robert Hancock <[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
- 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: make PROT_WRITE imply PROT_READ
- Next by Date: Re: [PATCH] cardbus: revert IO window limit
- Previous by thread: Re: make PROT_WRITE imply PROT_READ
- Next by thread: Re: make PROT_WRITE imply PROT_READ
- Index(es):