linux-kernel - Re: [patch] slab: Do not use mempolicy for kmalloc

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:	Tue, 12 Sep 2006 10:36:54 -0700 (PDT)
From:	Christoph Lameter <christoph@...r.sgi.com>
To:	Ravikiran G Thirumalai <kiran@...lex86.org>
cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	Alok Kataria <alok.kataria@...softinc.com>,
	"Shai Fultheim (Shai@...lex86.org)" <shai@...lex86.org>,
	Christoph Lameter <clameter@...r.sgi.com>
Subject: Re: [patch] slab: Do not use mempolicy for kmalloc_node

On Tue, 12 Sep 2006, Ravikiran G Thirumalai wrote:

> The slab should follow the specified memory policy for kmalloc allocations,
> which it does.  However, for kmalloc_node allocations, slab should
> serve the object from the requested node irrespective of memory policy.
> This seems to be broken in slab code.  Following patch fixes this.

This is not complete. Please see the discussion on GFP_THISNODE and the 
related patch to fix this issue 
http://marc.theaimsgroup.com/?l=linux-mm&m=115505682122540&w=2

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