From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: [Xen-devel] Live migration bug introduced in 2.6.32.16? Date: Wed, 16 Feb 2011 13:47:18 -0800 Message-ID: <20110216214718.GH5027@kroah.com> References: <4D41D3BA.7090602@gt.net> <201101280747.58019.hahn@univention.de> <1296204260.14780.6915.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1296204260.14780.6915.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: stable-bounces@linux.kernel.org Errors-To: stable-bounces@linux.kernel.org To: Ian Campbell Cc: Jeremy Fitzhardinge , "xen-devel@lists.xensource.com" , Konrad Rzeszutek Wilk , Philipp Hahn , Nathan March , stable@kernel.org List-Id: xen-devel@lists.xenproject.org On Fri, Jan 28, 2011 at 08:44:20AM +0000, Ian Campbell wrote: > (Please don't drop CC's when posting to xen-devel) > > On Fri, 2011-01-28 at 06:47 +0000, Philipp Hahn wrote: > > Hello, > > > > Am Donnerstag 27 Januar 2011 21:21:14 schrieb Nathan March: > > > It looks like a live migration bug may have been introduced in 2.6.32.16... > > ... > > > Note that this isn't consistent at all, I've got 6 dom0's and this only > > > happens when migrating certain directions between certain dom0's: > > > > Sounds like a problem very similar to mine. Please check if you have the > > pvclock-going-backwards-problem: > > > > The fix referenced by that thread (which turns out to be > http://marc.info/?l=linux-kernel&m=128811236726156&w=2) is upstream as > e7a3481c0246c8e45e79c629efd63b168e91fcda but didn't make it to the > stable trees (the resend which was what actually got applied appears to > have accidentally dropped the original's CC:stable@, oops). > > This is a fix for 489fb490dbf8dab0249ad82b56688ae3842a79e8 which went > into 2.6.32.16 as 1345126c761f0360dc108973bf73281d51945bc1 so the > timeline fits and the fix seems obviously correct. > > Greg, please can you queue e7a3481c0246c8e45e79c629efd63b168e91fcda for > 2.6.32.y longterm. The fix is already in 2.6.37-rc1 so its not needed > for the current stable branch. Now queued up. thanks, greg k-h