[lkml]   [2006]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] paravirt.h

    I don't see why paravirt ops is that much more sensitive
    than most other kernel code.

    > It would be a lot safer if we could have the struct paravirt_ops in
    > protected read-only const memory space, set it up in the core kernel
    > early on in boot when we play "guess todays hypervisor" and then make
    > sure it stays in read only (even to kernel) space.

    By default we don't make anything read only because that would
    mess up the 2MB kernel mapping.

    In general i don't think making select code in the kernel
    read only is a good idea, because as long as you don't
    protect everything including stacks etc. there will be always
    attack points where supposedly protected code relies
    on unprotected state. If someone can write to kernel
    memory you already lost.

    And it adds TLB pressure.


    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-08-22 15:47    [W:0.020 / U:22.900 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site