From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Vrabel <david.vrabel@citrix.com>
Subject: Re: Kernel bug from 3.0 (was phy disks and vifs timing
	out in DomU)
Date: Fri, 23 Sep 2011 13:49:16 +0100
Message-ID: <4E7C804C.1060904@citrix.com>
References: <4E31820C.5030200@overnetdata.com>
	<1311870512.24408.153.camel@cthulhu.hellion.org.uk>
	<4E3266DE.9000606@overnetdata.com>
	<20110803152841.GA2860@dumpdata.com>
	<4E4E3957.1040007@overnetdata.com>
	<20110819125615.GA26558@dumpdata.com>
	<4E56B132.9050708@overnetdata.com>
	<20110826142606.GA25511@dumpdata.com>
	<20110826144438.GA24836@dumpdata.com> <4E5E6843.7050206@citrix.com>
	<20110831170711.GB13642@dumpdata.com>
	<1314862972.28989.74.camel@zakaz.uk.xensource.com>
	<4E5FC197.7040004@goop.org>
	<1314904905.19389.28.camel@dagon.hellion.org.uk>
	<4E5FEC71.4090504@goop.org>
	<1314947875.28989.155.camel@zakaz.uk.xensource.com>
	<4E613BEF.30908@goop.org>
	<1315045639.19389.1683.camel@dagon.hellion.org.uk>
	<4E7C7CF5.1090907@overnetdata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4E7C7CF5.1090907@overnetdata.com>
List-Unsubscribe: <http://lists.xensource.com/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/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: Anthony Wright <anthony@overnetdata.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Keir Fraser <keir@xen.org>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, Ian Campbell <Ian.Campbell@eu.citrix.com>, Todd, Deshane <todd.deshane@xen.org>
List-Id: xen-devel@lists.xenproject.org

On 23/09/11 13:35, Anthony Wright wrote:
> 
> Is there any progress on an official patch for this [unsync'd vmalloc
> address space bug]? I have my own unofficial patch which places a
> vmalloc_sync_all() after every alloc_vm_area() call and it works, but
> from the thread it sounds like there should be a more sophisticated
> solution to the problem.

The simple patch (re-adding the vmalloc_sync_all()) has been applied to
3.1-rc7 and should be in the next 3.0-stable release.

I'm still working on a more elegant fix.

David