From: Gerd Knorr <kraxel@suse.de>
To: xen-devel@lists.xensource.com
Subject: bug: slab corruption (net backend?)
Date: Thu, 7 Jul 2005 11:41:32 +0200 [thread overview]
Message-ID: <20050707094132.GA29339@bytesex> (raw)
Hi,
With the small debug patch below and CONFIG_DEBUG_SLAB=y I get
plenty of these messages in the dom0 kernel log as soon as I
start a domU:
Slab corruption: start=dc423000, len=4096
Slab name: xen-skb
000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
This is hg1a7383f849896e60f8be631c96fa2b461f502615.
any idea?
Gerd
Index: linux-2.6.11/mm/slab.c
===================================================================
--- linux-2.6.11.orig/mm/slab.c 2005-03-02 08:38:38.000000000 +0100
+++ linux-2.6.11/mm/slab.c 2005-07-07 11:31:47.000000000 +0200
@@ -1007,6 +1007,9 @@ static void print_objinfo(kmem_cache_t *
int i, size;
char *realobj;
+ if (cachep->name) {
+ printk(KERN_ERR "Slab name: %s\n", cachep->name);
+ }
if (cachep->flags & SLAB_RED_ZONE) {
printk(KERN_ERR "Redzone: 0x%lx/0x%lx.\n",
*dbg_redzone1(cachep, objp),
next reply other threads:[~2005-07-07 9:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 9:41 Gerd Knorr [this message]
2005-07-07 10:11 ` bug: slab corruption (net backend?) Steven Hand
2005-07-07 11:35 ` Gerd Knorr
2005-07-07 12:05 ` Keir Fraser
2005-07-07 12:22 ` Gerd Knorr
2005-07-07 12:48 ` Gerd Knorr
2005-07-07 13:17 ` Gerd Knorr
2005-07-07 14:05 ` Keir Fraser
2005-07-07 14:18 ` Gerd Knorr
2005-07-07 14:41 ` Gerd Knorr
2005-07-07 16:06 ` Nivedita Singhvi
2005-07-11 13:25 ` Gerd Knorr
2005-07-11 13:37 ` Keir Fraser
2005-07-11 14:29 ` Bin Ren
2005-07-07 15:54 ` Gerd Knorr
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=20050707094132.GA29339@bytesex \
--to=kraxel@suse.de \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.