Re: [PATCH 2.6.20-rc1 00/10] Kernel memory leak detector 0.13

From: Ingo Molnar
Date: Wed Dec 27 2006 - 12:00:10 EST

* Catalin Marinas <catalin.marinas@xxxxxxxxx> wrote:

> On 17/12/06, Ingo Molnar <mingo@xxxxxxx> 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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at