lkml.org 
[lkml]   [2000]   [Sep]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: the new VM

    On Tue, 26 Sep 2000, Pavel Machek wrote:

    > Okay, I'm user on small machine and I'm doing stupid thing: I've got
    > 6MB ram, and I keep inserting modules. I insert module_1mb.o. Then I
    > insert module_1mb.o. Repeat. How does it end? I think that
    > kmalloc(GFP_KERNEL) *has* to return NULL at some point.

    if a stupid root user keeps inserting bogus modules :-) then thats a
    problem, no matter what. I can DoS your system if given the right to
    insert arbitrary size modules, even if kmalloc returns NULL. For such
    things explicit highlevel protection is needed - completely independently
    of the VM allocation issues. Returning NULL in kmalloc() is just a way to
    say: 'oops, we screwed up somewhere'. And i'd suggest to not work around
    such screwups by checking for NULL and trying to handle it. I suggest to
    rather fix those screwups.

    the __GFP_SOFT suggestion handles these things nicely.

    Ingo

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 12:38    [W:4.105 / U:0.332 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site