The patch titled
gfp_thisnode-for-the-slab-allocator-v2 fix 3
has been removed from the -mm tree. Its filename is
gfp_thisnode-for-the-slab-allocator-v2-fix-3.patch
This patch was dropped because it was folded into gfp_thisnode-for-the-slab-allocator-v2.patch
------------------------------------------------------
Subject: gfp_thisnode-for-the-slab-allocator-v2 fix 3
From: Christoph Lameter <clameter@xxxxxxx>
On Thu, 21 Sep 2006, Andrew Morton wrote:
> I guess the below will fix it. But Christoph's machine would have oopsed
> too, if it had called fallback_alloc() this early. So presumably it did
> not. But yours does. I wonder why?
Hmmm... Fallback during boot? Any zones that have no ZONE_NORMAL memory?
The right fix though is to check for a NULL memory policy in slab_node.
This is the way other mempol functions behave.
Signed-off-by: Christoph Lameter <clameter@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
mm/mempolicy.c | 4 +++-
1 files changed, 3 insertions(+), 1 deletion(-)
diff -puN mm/mempolicy.c~gfp_thisnode-for-the-slab-allocator-v2-fix-3 mm/mempolicy.c
--- a/mm/mempolicy.c~gfp_thisnode-for-the-slab-allocator-v2-fix-3
+++ a/mm/mempolicy.c
@@ -1136,7 +1136,9 @@ static unsigned interleave_nodes(struct
*/
unsigned slab_node(struct mempolicy *policy)
{
- switch (policy->policy) {
+ int pol = policy ? policy->policy : MPOL_DEFAULT;
+
+ switch (pol) {
case MPOL_INTERLEAVE:
return interleave_nodes(policy);
_
Patches currently in -mm which might be from clameter@xxxxxxx are
origin.patch
slab-fix-kmalloc_node-applying-memory-policies-if-nodeid-==-numa_node_id.patch
add-numa_build-definition-in-kernelh-to-avoid-ifdef.patch
disable-gfp_thisnode-in-the-non-numa-case.patch
gfp_thisnode-for-the-slab-allocator-v2.patch
gfp_thisnode-for-the-slab-allocator-v2-fix-3.patch
add-node-to-zone-for-the-numa-case.patch
add-node-to-zone-for-the-numa-case-fix.patch
do-not-allocate-pagesets-for-unpopulated-zones.patch
zone_statistics-use-hot-node-instead-of-cold-zone_pgdat.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
