From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: New release candidates for Xen 3.3.2 and 3.4.1 Date: Tue, 23 Jun 2009 20:03:26 +0100 Message-ID: References: <4A411439.6020904@Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4A411439.6020904@Sun.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: Frank van der Linden Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 23/06/2009 18:43, "Frank van der Linden" wrote: >> Is this a regression relative to 3.3.1, do you know? That would make it more >> likely a blocker. >> >> -- Keir >> > I can't say for sure, unfortunately, since the tests that uncovered this > weren't run on earlier incarnations of our 3.3-based tree. > > It seems that a few shadow fixes have gone in post 3.3.1, but I have no > evidence that these would cause this particular. problem. It might be sensible to try, depending on how long the bug takes to reproduce. If you can be sure that it does not repro with 3.3.1 that has two advantages for you: firstly, I would hold up the 3.3.2 release, and secondly the set of changesets to search for the bug is greatly reduced. -- Keir