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

[Ingo Molnar <mingo@elte.hu>]

* Ingo Molnar <mingo@elte.hu> wrote:

> > 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.

furthermore, i'd put "hardirq" into the comm copy if in_hardirq() is 
true, and i'd put "softirq" into the comm copy if !in_hardirq && 
in_softirq(). That way the allocation is not attributed to a process 
that has no real connection to it.

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