| 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
| ||
|
Message-Id: <1167236618.3281.3986.camel@laptopd505.fenrus.org> Date: Wed, 27 Dec 2006 17:23:38 +0100 From: Arjan van de Ven <arjan@...radead.org> To: Catalin Marinas <catalin.marinas@...il.com> Cc: Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2.6.20-rc1 00/10] Kernel memory leak detector 0.13 On Wed, 2006-12-27 at 16:14 +0000, Catalin Marinas wrote: > On 17/12/06, Ingo Molnar <mingo@...e.hu> 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? well you take the lock from irq context, which means it needs to use _irqsave/restore everywhere. (and all locks taken inside it must be irq safe as well) maybe.. not use comm in irq context? it doesn't actually mean anything there anyway... -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org - 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/
Powered by blists - more mailing lists