From: Greg KH <greg@kroah.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Philipp Hahn <hahn@univention.de>, Nathan March <nathan@gt.net>,
stable@kernel.org
Subject: Re: [Xen-devel] Live migration bug introduced in 2.6.32.16?
Date: Wed, 16 Feb 2011 13:47:18 -0800 [thread overview]
Message-ID: <20110216214718.GH5027@kroah.com> (raw)
In-Reply-To: <1296204260.14780.6915.camel@zakaz.uk.xensource.com>
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:
> > <http://lists.xensource.com/archives/html/xen-users/2011-01/msg00375.html>
>
> 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
prev parent reply other threads:[~2011-02-16 21:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 20:21 Live migration bug introduced in 2.6.32.16? Nathan March
2011-01-27 20:36 ` Konrad Rzeszutek Wilk
2011-01-27 20:42 ` Nathan March
2011-01-27 20:57 ` Ian Campbell
2011-01-27 22:54 ` Nathan March
2011-01-27 23:27 ` Konrad Rzeszutek Wilk
2011-01-28 8:53 ` Pasi Kärkkäinen
2011-01-28 0:51 ` Nathan March
2011-01-28 6:47 ` Philipp Hahn
2011-01-28 8:44 ` Ian Campbell
2011-01-28 18:44 ` Nathan March
2011-02-04 14:17 ` Ian Campbell
2011-02-04 14:46 ` [Xen-devel] " Greg KH
2011-02-04 14:51 ` Ian Campbell
2011-02-16 21:47 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110216214718.GH5027@kroah.com \
--to=greg@kroah.com \
--cc=Ian.Campbell@citrix.com \
--cc=hahn@univention.de \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=nathan@gt.net \
--cc=stable@kernel.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.