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/
Home Products Support Community News


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

To: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] bug: slab corruption (net backend?)
From: Gerd Knorr <kraxel@xxxxxxx>
Date: Thu, 7 Jul 2005 13:35:14 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 07 Jul 2005 11:38:54 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <E1DqTLV-00068D-00@xxxxxxxxxxxxxxxxx>
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>
References: <20050707094132.GA29339@bytesex> <E1DqTLV-00068D-00@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
> One thing to check is what the underlying pfn and/or mfn is for the 
> relevant slabs(s) which could point to an allocation issue. 

Looks like xen allocates via kmem_cache_alloc() and releases via
kfree(), which is illegal according to a comment in mm/slab.c

Seems to work nevertheless, but maybe it's pure luck and we'll
hit a bug sooner or later.  I'll try fix this and see if the
problem goes away then ...


panic("it works"); /* avoid being flooded with debug messages */

Xen-devel mailing list