lkml.org 
[lkml]   [1998]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    Subjectlockd freeing memory it doesn't own?
    Hi Olaf,

    I'm locking at fs/lockd/clntproc.c and its use of system_utsname.

    Specifically, in clntproc.c, there is some code to set
    lock->caller and alock->caller to system_utsname. I can't figure
    out where these things are getting used. Ultimately, though,
    nlmclnt_freegrantargs calls kfree on it.

    Could you help me understand this "caller" field and the memory
    management that is going on here?

    Thanks,

    Michael Chastain
    <mailto:mec@shout.net>
    "love without fear"

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu

    \
     
     \ /
      Last update: 2005-03-22 13:42    [W:0.030 / U:88.776 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site