On Thu, Sep 14, 2006 at 06:39:47PM -0700, [EMAIL PROTECTED] wrote: > Make PROT_WRITE imply PROT_READ for a number of architectures which > don't support write only in hardware.
Why don't we WARN where PROT_WRITE is used w/o PROT_READ? Do non-trivial or non-contrived applications really use PROT_WRITE and assume reads are OK? It seems once we do this there will be little or no chance of ever doing write-only mappings should we want to in the future using this mechanism. We could just update the definition of PROT_WRITE in the userspace headers... - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
