linux-kernel - Re: [i386] Use page allocator to allocate threadinfo structure

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: <20070405083021.GR2986@holomorphy.com>
Date:	Thu, 5 Apr 2007 01:30:21 -0700
From:	William Lee Irwin III <wli@...omorphy.com>
To:	Christoph Lameter <clameter@....com>
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [i386] Use page allocator to allocate threadinfo structure

On Wed, Apr 04, 2007 at 05:40:31PM -0700, Christoph Lameter wrote:
> Replace the calls to kmalloc with calls into the page allocator.
> An alternate solution may be to create a custom slab cache where the 
> alignment is set to PAGE_SIZE. That would allow slub debugging to be 
> applied to the threadinfo structure.
> Signed-off-by: Christoph Lameter <clameter@....com>

This was originally made a slab allocation as a preparatory cleanup
for things that were never merged, and are never likely to be. One
might as well revert it, though it does make stack space usage
slightly more difficult to account for.


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