WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] bug: slab corruption (net backend?)

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] bug: slab corruption (net backend?)
From: Gerd Knorr <kraxel@xxxxxxx>
Date: Thu, 7 Jul 2005 11:41:32 +0200
Delivery-date: Thu, 07 Jul 2005 09:43:49 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
  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),

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel