[lkml]   [2006]   [Dec]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 2.6.20-rc1 00/10] Kernel memory leak detector 0.13
    On 27/12/06, Ingo Molnar <> wrote:
    > * Catalin Marinas <> wrote:
    > > On 17/12/06, Ingo Molnar <> wrote:
    > > >it would be nice to record 1) the jiffies value at the time of
    > > >allocation, 2) the PID and the comm of the task that did the allocation.
    > > >The jiffies timestamp would be useful to see the age of the allocation,
    > > >and the PID/comm is useful for context.
    > >
    > > Trying to copy the comm with get_task_comm, I get the lockdep report
    > > below, caused by acquiring the task's alloc_lock. Any idea how to go
    > > around this?
    > just memcpy p->comm without any locking. It's for the current task,
    > right? That does not need any locking.

    Yes, it is for the current task. I also added an in_interrupt() test
    since the current->comm is not relevant in this case as Arjan pointed

    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-12-27 18:05    [W:0.025 / U:1.688 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site