From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gerd Knorr <kraxel@suse.de>
Subject: Re: bug: slab corruption (net backend?)
Date: 07 Jul 2005 17:54:07 +0200
Message-ID: <873bqqhasg.fsf@bytesex.org>
References: <20050707094132.GA29339@bytesex>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20050707094132.GA29339@bytesex>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Gerd Knorr <kraxel@suse.de> writes:

> 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

After digging in the netback code I'm not sure any more this is a real
bug.  Could also be the slab debugging can deal with the page mapping
tricks the netback driver does when sending/receiving packets.  The
start address mentioned referes to a page allocated via alloc_mfn() in
netback.c ...

  Gerd

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