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:	Fri, 13 Oct 2006 12:05:19 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Will Schmidt <will_schmidt@...t.ibm.com>
cc:	linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org
Subject: Re: kernel BUG in __cache_alloc_node at  linux-2.6.git/mm/slab.c:3177!

On Fri, 13 Oct 2006, Will Schmidt wrote:

>     Am seeing a crash on a power5 LPAR when booting the linux-2.6 git
> tree.  It's fairly early during boot, so I've included the whole log
> below.   This partition has 8 procs, (shared, including threads), and
> 512M RAM.  

This looks like slab bootstrap. You are bootstrapping while having 
zonelists build with zones that are only going to be populated later? 
This will lead to incorrect NUMA placement of lots of slab structures on 
bootup.

Check if the patch below may cure the oops. Your memory is likely 
still placed on the wrong numa nodes since we have to fallback from 
the intended node.

Index: linux-2.6/mm/slab.c
===================================================================
--- linux-2.6.orig/mm/slab.c	2006-10-13 11:59:55.000000000 -0700
+++ linux-2.6/mm/slab.c	2006-10-13 12:03:15.000000000 -0700
@@ -3154,7 +3154,8 @@ void *fallback_alloc(struct kmem_cache *
 
 	for (z = zonelist->zones; *z && !obj; z++)
 		if (zone_idx(*z) <= ZONE_NORMAL &&
-				cpuset_zone_allowed(*z, flags))
+				cpuset_zone_allowed(*z, flags) &&
+				(*z)->free_pages)
 			obj = __cache_alloc_node(cache,
 					flags | __GFP_THISNODE,
 					zone_to_nid(*z));
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ