From: Andrew Morton <akpm@osdl.org>
To: "R. J. Wysocki" <rjwysocki@sisk.pl>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@muc.de>
Subject: Re: 2.6.7-mm3: Kernel BUG on dual Opteron with DEBUG_SLAB
Date: Mon, 28 Jun 2004 16:12:56 -0700 [thread overview]
Message-ID: <20040628161256.4d0365ab.akpm@osdl.org> (raw)
In-Reply-To: <200406282129.35120.rjwysocki@sisk.pl>
"R. J. Wysocki" <rjwysocki@sisk.pl> wrote:
>
> Kernel BUG at mempolicy:585
OK, this is a straight use-after-free bug:
--- 25/mm/mempolicy.c~a 2004-06-28 15:46:42.000000000 -0700
+++ 25-akpm/mm/mempolicy.c 2004-06-28 15:48:25.000000000 -0700
@@ -582,7 +582,7 @@ static struct zonelist *zonelist_policy(
break;
default:
nd = 0;
- BUG();
+ printk("%s: policy=%x\n", __FUNCTION__, policy->policy);
}
return NODE_DATA(nd)->node_zonelists + (gfp & GFP_ZONEMASK);
}
linux:/home/akpm> dmesg -s 1000000|grep zonelist
Built 1 zonelists
zonelist_policy: policy=6b6b
zonelist_policy: policy=6b6b
Andi, could you take a look? Enabling CONFIG_DEBUG_SLAB and CONFIG_NUMA
triggers it 100% of the time.
next prev parent reply other threads:[~2004-06-28 23:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 6:31 2.6.7-mm3 Andrew Morton
2004-06-27 9:04 ` 2.6.7-mm3 Joshua Kwan
2004-06-27 11:38 ` 2.6.7-mm3 [broken serial console and Kernel BUG on dual Opteron] R. J. Wysocki
2004-06-28 7:19 ` Andrew Morton
2004-06-28 19:18 ` R. J. Wysocki
2004-06-28 19:29 ` 2.6.7-mm3: Kernel BUG on dual Opteron with DEBUG_SLAB R. J. Wysocki
2004-06-28 23:12 ` Andrew Morton [this message]
2004-06-27 14:17 ` [patch] 2.6.7-mm3 ALSA gus compile error Adrian Bunk
2004-06-27 22:51 ` 2.6.7-mm3 Joseph Fannin
2004-06-28 15:03 ` 2.6.7-mm3 (compile stats) John Cherry
2004-06-28 19:27 ` [PATCH 2.6.7-mm3] cirrusfb: minor fixes Francois Romieu
2004-06-28 21:59 ` David Eger
2004-06-28 22:42 ` Francois Romieu
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=20040628161256.4d0365ab.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rjwysocki@sisk.pl \
/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
all inboxes | Powered by JetHome®