linux-kernel - Re: [PATCH 2.6.28-rc5 01/11] kmemleak: Add the base support

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]

Message-ID: <84144f020811240019u53754541kf585b6a21462db3b@mail.gmail.com>
Date:	Mon, 24 Nov 2008 10:19:45 +0200
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Catalin Marinas" <catalin.marinas@....com>
Cc:	linux-kernel@...r.kernel.org, cl@...ux-foundation.org
Subject: Re: [PATCH 2.6.28-rc5 01/11] kmemleak: Add the base support

On Mon, Nov 24, 2008 at 10:16 AM, Pekka Enberg <penberg@...helsinki.fi> wrote:
> OK, but I don't really see any fundamental reason why we couldn't do
> this. I mean, from my point of view, it would be better to add
> specialized hooks (i.e. separate allocation paths for the kmemleak hooks
> that avoid any issues) inside the SLAB allocators rather than invent a
> separate allocator. As an example,

Oops, I don't know where that "as an example" part came from so just
ignore it. :-)
--
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/