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] Re: [patch 1/1] ext4-fix-dirty-extent-when-origin-leaf-e

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Re: [patch 1/1] ext4-fix-dirty-extent-when-origin-leaf-extent-reac.patch
From: "Olivier B." <xen.list@xxxxxxxxx>
Date: Wed, 28 Sep 2011 01:41:30 +0200
Delivery-date: Tue, 27 Sep 2011 16:41:28 -0700
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=daevel.fr; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=cud5uQ1xD61+oVyZDqnueFD6Zx9LkAGSU+yEMVkDnU8=; b=OpHSwq6kPa5j8KB7nV3id5Eda54IfIK0NN1qKJV2z8iwWQkP0o0UOKbhurnCUnmhG5oEaYj4yHc+2ZFEEzYdxX2A60KNG5A98hkqZ8EdL38T3Wu26gRj4DcfMkF9CtMx;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110927193523.GB3309@xxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BLU157-W499E698F650F554E645F9DDA1C0@xxxxxxx> <20110906145347.GA4133@xxxxxxxxxxxx> <BLU157-W4106FA4CF4EBA78C63FDA0DA1C0@xxxxxxx> <4E666C86.5090707@xxxxxxxx> <BLU157-W323C330706CB8D7E976BC3DA1F0@xxxxxxx> <BLU157-W7DABA5FE01C50C29B1A64DA060@xxxxxxx> <BLU157-W25EB1EAC24CC11FA14859ADAF20@xxxxxxx> <20110926142808.GG4102@xxxxxxxxxxxxxxxxx> <20110927193523.GB3309@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110807 Icedove/5.0
On 27/09/2011 21:35, Ted Ts'o wrote:
On Mon, Sep 26, 2011 at 10:28:08AM -0400, Konrad Rzeszutek Wilk wrote:

    Attached is the fix, verified in our env.

So.. you are asking for this upstream git commit to be back-ported
to 2.6.32, right?

I'm curious --- is there a good reason why Xen users are using an
upstream 2.6.32 kernel?  If they are using a distro kernel, fine, but
then the distro kernel should be providing the support.  But at this
point, 2.6.32 is so positively *ancient* that, I'm personally not
interesting in providing free, unpaid distro support for users who
aren't willing to either (a) pay $$$ and get a supported distro
kernel, or (b) use a much more modern kernel.  At this point, Guest
and Host Xen support is available in 3.0 kernels, so there's really no
excuse, right?

                                                - Ted


In my case, for Dom0 I use the 2.6.32 kernel from my distrib, because it's 
stable.
I have stability problems with the kernel 3.0 on Dom0, and as I haven't 
physical access neither kvm or serial port, I don't know what to report... It 
just hang randomly, without any line in logs.

Does the Xen support on 3.0 kernels should be considered stable ?

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