From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: make xen/stable-2.6.32.x pvops branch the default? Date: Tue, 08 Jun 2010 09:38:16 -0700 Message-ID: <4C0E71F8.4050401@goop.org> References: <20100608111501.GP17817@reaktio.net> <4C0E667F.2040306@goop.org> <20100608161545.GB4900@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100608161545.GB4900@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: Bastian Blank , xen-devel@lists.xensource.com, Jan Beulich , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 06/08/2010 09:15 AM, Konrad Rzeszutek Wilk wrote: > On top of that, what about that udev(new version) race condition? I > think James and Bastian both provided a patch - does it make sense to > merge it in both branches (.31 and .32)? > I've got James' patch in .32 at the moment. I was about to apply Bastien's fix, but Jan raised some comments, but Bastien didn't reply. So I stared into space for a while. I'd like to get a definitive fix that everyone agrees on. Is there also a problem in .31? Is it triggered by a new udev rather than a kernel version? J