linux-kernel - Re: [RFC PATCH 4/5] kmemtrace: SLUB hooks.

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] [day] [month] [year] [list]

Message-Id: <1216053054.6762.6.camel@penberg-laptop>
Date:	Mon, 14 Jul 2008 19:30:54 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	Christoph Lameter <cl@...ux-foundation.org>
Subject: Re: [RFC PATCH 4/5] kmemtrace: SLUB hooks.

Hi Eduard-Gabriel,

On Fri, 11 Jul 2008 11:45:59 +0300
> > Oh, I missed this on the first review. Here we have, like in SLOB,
> > page allocator pass-through, so wouldn't KIND_PAGES be more
> > appropriate?

On Fri, 2008-07-11 at 23:19 +0300, Eduard - Gabriel Munteanu wrote:
> The rationale was to be able to trace how kmalloc()s perform, no matter
> what the allocator does behind the scenes. Presumably, the developer
> would know what kmalloc() really does with an allocation request.
> 
> Does this sound okay?

Fine with me.

		Pekka

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