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

Re: [Xen-devel] null pointer in domU

To: Tupshin Harper <tupshin@xxxxxxxxxxx>
Subject: Re: [Xen-devel] null pointer in domU
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 28 Apr 2005 10:21:53 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 28 Apr 2005 09:18:07 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <427049F9.2010605@xxxxxxxxxxx>
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: <427049F9.2010605@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 28 Apr 2005, at 03:27, Tupshin Harper wrote:

After a couple weeks of uptime, my domU router (routing between 3 nics)
crashed with the following (hand copied as it was locked up hard.

The dom0 was fine, and no problems with the other domUs.

Dom0 running 2.6.11-ac1-xen0 and domU running 2.6.11-ac1-xenU
Both are basically 2.6.11-xen + alan's ac patch to get additional
network driver support.

domU got a response from dom0 containing an unexpected request id. domU tried to lookup the skbuff corresponding to the id, but read garbage (because the id was not currently in use). It crashed when it tried to dereference the garbage skbuff pointer.

This is rather nasty -- it's not clear whether dom0 or domU is at fault (dom0 may have forgotten about the id, or corrupted its own state, or the response from dom0 could be at fault). And it must be hard to trigger as we have had no other reports of this. :-(

 -- Keir


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

<Prev in Thread] Current Thread [Next in Thread>