[lkml]   [2006]   [Jun]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: make PROT_WRITE imply PROT_READ
    On 6/23/06, Arjan van de Ven <> wrote:
    > you ask for it, and the kernel is supposed to deliver the best behavior
    > it can.

    The kernel should provide

    - a stable, reliable interface

    - a consistent interface at least accross architectures, maybe even platforms

    Providing write-only support for memory falls into none of these
    categories. When Jason and I discussed this my position actually was
    to disallow PROT_WRITE without PROT_READ completely, making it an
    error of mmap and mprotect. That's perfectly legal according to POSIX
    and it will teach those who write broken code like this.

    Jason's proposal to implicitly set PROT_READ is the second best
    solution. It gets rid of the error cases which a developer might not
    notice, either because of lucky circumstances or details of the

    The reality is that almost no platform can really implement write-only
    memory. RISC architectures implement sub-word write as word reads,
    modify, word write. And even for CISC archs the compiler, for
    instance, might decide to read memory, be it for prefetching or
    explicit write-combining.

    I'm strongly in favor of adding of adding one of the two possible
    patches (forbidding, implicitly setting PROT_READ). This will help
    preventing these kinds of programming mistakes from spreading and we
    already _know_ that there are such programs out there.
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-06-24 20:48    [W:0.021 / U:17.708 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site