Re: user malloc from kernel

From: Pawel Jakub Dawidek (nick_at_garage.freebsd.pl)
Date: 09/29/03

  • Next message: Andrew Kinney: "Re: Can not dump on raid dev?" 
    Date: Mon, 29 Sep 2003 21:12:58 +0200
To: earthman <earthman@inbox.ru>, freebsd-hackers@freebsd.org

    On Mon, Sep 29, 2003 at 06:56:13PM +0300, Peter Pentchev wrote:
    +> I mean, won't the application's memory manager attempt to allocate the
    +> next chunk of memory right over the region that you have stolen with
    +> this brk(2) invocation? Thus, when the application tries to write into
    +> its newly-allocated memory, it will overwrite the data that the kernel
    +> has placed there, and any attempt to access the kernel's data later will
    +> fail in wonderfully unpredictable ways :)

    I'm not sure if newly allocated memory will overwrite memory allocated
    in kernel, but for sure process is able to write to this memory.

    Sometime ago I proposed model which will allow to remove all copyin(9)
    calls and many copyout(9), but I'm not so skilled in VM to implement it. 

    -- 
Pawel Jakub Dawidek                       pawel@dawidek.net
UNIX Systems Programmer/Administrator     http://garage.freebsd.pl
Am I Evil? Yes, I Am!                     http://cerber.sourceforge.net

  • Next message: Andrew Kinney: "Re: Can not dump on raid dev?"

    Relevant Pages