All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan March <nathan@gt.net>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Philipp Hahn <hahn@univention.de>
Subject: Re: Live migration bug introduced in 2.6.32.16?
Date: Fri, 28 Jan 2011 10:44:51 -0800	[thread overview]
Message-ID: <4D430EA3.10203@gt.net> (raw)
In-Reply-To: <1296204260.14780.6915.camel@zakaz.uk.xensource.com>


> 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

I can confirm that e7a3481c0246c8e45e79c629efd63b168e91fcda has fixed my 
migration problems. Thanks for all the quick help everyone, very much 
appreciated.

- Nathan

  reply	other threads:[~2011-01-28 18:44 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 [this message]
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

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=4D430EA3.10203@gt.net \
    --to=nathan@gt.net \
    --cc=Ian.Campbell@citrix.com \
    --cc=hahn@univention.de \
    --cc=konrad.wilk@oracle.com \
    --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.