lkml.org 
[lkml]   [2011]   [May]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [PATCH] Don't mlock guardpage if the stack is growing up
    On Wed, May 11, 2011 at 1:42 AM, Milan Broz <mbroz@redhat.com> wrote:
    >
    > Another one is cryptsetup [..]

    Quite frankly, all security-related uses should always be happy about
    a "MCL_SPARSE" model, since there is no point in ever bringing in
    pages that haven't been used. The whole (and only) point of
    mlock[all]() for them is the "avoid to push to disk" issue.

    I do wonder if we really should ever do the page-in at all. We might
    simply be better off always just saying "we'll lock pages you've
    touched, that's it".

    Linus


    \
     
     \ /
      Last update: 2011-05-12 04:15    [W:4.621 / U:0.204 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site