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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 27 Dec 2006 17:56:39 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Catalin Marinas <catalin.marinas@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.20-rc1 00/10] Kernel memory leak detector 0.13


* Ingo Molnar <mingo@...e.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/