From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Nishanth Aravamudan <nacc@us.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm@kvack.org, lee.schermerhorn@hp.com, bob.picco@hp.com,
mel@skynet.ie
Subject: Re: [BUG] at mm/slab.c:3320
Date: Thu, 10 Jan 2008 00:28:59 +0530 [thread overview]
Message-ID: <20080109185859.GD11852@skywalker> (raw)
In-Reply-To: <Pine.LNX.4.64.0801090949440.10163@schroedinger.engr.sgi.com>
On Wed, Jan 09, 2008 at 09:50:56AM -0800, Christoph Lameter wrote:
> On Tue, 8 Jan 2008, Nishanth Aravamudan wrote:
>
> > Do we (perhaps you already have done so, Christoph), want to validate
> > any other users of numa_node_id() that then make assumptions about the
> > characteristics of the nid? Hrm, that sounds good in theory, but seems
> > hard in practice?
>
> Hmmm... The main allocs are the slab allocations. If we fallback in
> kmalloc etc then we are fine for the common case. SLUB falls back
> correctly. Its just the weird nesting of functions in SLAB that has made
> this a bit difficult for that allocator.
>
This patch didn't work. I still see
------------[ cut here ]------------
kernel BUG at mm/slab.c:3323!
invalid opcode: 0000 [#1] PREEMPT SMP
Modules linked in:
Pid: 0, comm: swapper Not tainted (2.6.24-rc5-autokern1 #1)
EIP: 0060:[<c01816fa>] EFLAGS: 00010046 CPU: 0
EIP is at ____cache_alloc_node+0x1c/0x130
EAX: e2c005c0 EBX: 00000000 ECX: 00000001 EDX: 000000d0
ESI: 00000000 EDI: e2c005c0 EBP: c03fef68 ESP: c03fef48
DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
Process swapper (pid: 0, ti=c03fe000 task=c03cbd80 task.ti=c03fe000)
Stack: c03cbd80 c03fef60 c017ac2a 00000001 000000d0 00000000 000000d0 e2c005c0
c03fef7c c018156a 0002080c 00099800 00000000 c03fefa8 c0181a90 22222222
22222222 00000246 c01395b5 000000d0 e2c005c0 0002080c 00099800 c03d2cec
Call Trace:
[<c0105e23>] show_trace_log_lvl+0x19/0x2e
[<c0105ee5>] show_stack_log_lvl+0x99/0xa1
[<c010603f>] show_registers+0xb3/0x1e9
[<c0106301>] die+0x11b/0x1fe
[<c02f2de4>] do_trap+0x8e/0xa8
[<c01065cd>] do_invalid_op+0x88/0x92
[<c02f2bb2>] error_code+0x72/0x78
[<c018156a>] alternate_node_alloc+0x5b/0x60
[<c0181a90>] kmem_cache_alloc+0x56/0x272
[<c01395b5>] create_pid_cachep+0x4c/0xec
[<c0410e65>] pidmap_init+0x2f/0x6e
[<c0402715>] start_kernel+0x1ca/0x23e
[<00000000>] 0x0
=======================
Code: ff eb 02 31 ff 89 f8 83 c4 10 5b 5e 5f 5d c3 55 89 e5 57 89 c7 56 53 83 ec 14 89 55 f0 89 4d ec 8b b4 88 88 02 00 00 85 f6 75 04 <0f> 0b eb fe e8 f4 ee ff ff 8d 46 24 89 45 e4 e8 c0 0e 17 00 8b
EIP: [<c01816fa>] ____cache_alloc_node+0x1c/0x130 SS:ESP 0068:c03fef48
Kernel panic - not syncing: Attempted to kill the idle task!
-- 0:conmux-control -- time-stamp -- Jan/09/08 10:21:55 --
-- 0:conmux-control -- time-stamp -- Jan/09/08 10:33:39 --
(bot:conmon-payload) disconnected
diff --git a/mm/slab.c b/mm/slab.c
index 2e338a5..34279d8 100644
--- a/mm/slab.c
+++ b/mm/slab.c
@@ -2977,6 +2977,9 @@ retry:
}
l3 = cachep->nodelists[node];
+ if (!l3)
+ return NULL;
+
BUG_ON(ac->avail > 0 || !l3);
spin_lock(&l3->list_lock);
@@ -3439,8 +3442,14 @@ __do_cache_alloc(struct kmem_cache *cache, gfp_t flags)
* We may just have run out of memory on the local node.
* ____cache_alloc_node() knows how to locate memory on other nodes
*/
- if (!objp)
- objp = ____cache_alloc_node(cache, flags, numa_node_id());
+ if (!objp) {
+ int node_id = numa_node_id();
+ if (likely(cache->nodelists[node_id])) /* fast path */
+ objp = ____cache_alloc_node(cache, flags, node_id);
+ else /* this function can do good fallback */
+ objp = __cache_alloc_node(cache, flags, node_id,
+ __builtin_return_address(0));
+ }
out:
return objp;
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-01-09 18:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071220100541.GA6953@skywalker>
2007-12-25 22:05 ` [BUG] at mm/slab.c:3320 Andrew Morton
2007-12-27 15:32 ` Aneesh Kumar K.V
2007-12-27 19:31 ` Christoph Lameter
[not found] ` <20071228051959.GA6385@skywalker>
[not found] ` <Pine.LNX.4.64.0801021227580.20331@schroedinger.engr.sgi.com>
2008-01-03 15:50 ` Aneesh Kumar K.V
2008-01-04 0:33 ` Nishanth Aravamudan
2008-01-07 1:23 ` KAMEZAWA Hiroyuki
2008-01-07 18:10 ` Christoph Lameter
2008-01-08 1:40 ` KAMEZAWA Hiroyuki
2008-01-08 5:38 ` Christoph Lameter
2008-01-08 7:11 ` Aneesh Kumar K.V
2008-01-09 6:50 ` Nishanth Aravamudan
2008-01-09 17:50 ` Christoph Lameter
2008-01-09 18:58 ` Aneesh Kumar K.V [this message]
2008-01-09 19:23 ` Christoph Lameter
2008-01-09 21:47 ` Nishanth Aravamudan
2008-01-09 21:51 ` Christoph Lameter
2008-01-09 22:13 ` Nishanth Aravamudan
2008-01-10 0:02 ` Christoph Lameter
2008-01-17 12:31 ` Pekka Enberg
2008-01-17 14:32 ` Christoph Lameter
2008-01-17 14:36 ` Pekka J Enberg
2008-01-17 15:05 ` Christoph Lameter
2008-01-17 15:25 ` Aneesh Kumar K.V
2008-01-17 16:58 ` Christoph Lameter
2008-01-17 17:42 ` Aneesh Kumar K.V
2008-01-17 21:40 ` Mel Gorman
2008-01-17 20:47 ` Pekka J Enberg
2008-01-20 0:58 ` Mel Gorman
2008-01-22 20:20 ` Christoph Lameter
2008-01-10 4:13 ` Aneesh Kumar K.V
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080109185859.GD11852@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=bob.picco@hp.com \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
--cc=nacc@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).