From: "Jan Beulich" <JBeulich@novell.com>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: Ashish Bijlani <ashish.bijlani@gmail.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: live migration fails (assert in shadow_hash_delete)
Date: Fri, 26 Feb 2010 14:49:41 +0000 [thread overview]
Message-ID: <4B87ED950200007800031879@vpn.id2.novell.com> (raw)
In-Reply-To: <20100226142217.GU368@whitby.uk.xensource.com>
>>> Tim Deegan <Tim.Deegan@citrix.com> 26.02.10 15:22 >>>
>Keir, I'm still seeing (different) crashes on unstable tip even with
>Jan's fix; the proximate cause is c/s 20954, which changes the paths
>taken when log-dirty mode is turned off after the live migration.
>
>Reverting c/s 20954 fixes migration for me and is probably the best
>thing to get the 4.0 release schedule going again. I'll try to find
>the actual bug at some later date.
So perhaps the fall-through there was really intended? I had pointed
out that these missing break statements looked suspicious, so maybe
it's simply that those two places should be annotated accordingly?
Jan
next prev parent reply other threads:[~2010-02-26 14:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 8:57 live migration fails (assert in shadow_hash_delete) Ashish Bijlani
2010-02-23 9:25 ` Tim Deegan
2010-02-23 10:19 ` Devdutt Patnaik
2010-02-23 10:25 ` Devdutt Patnaik
2010-02-23 10:46 ` Tim Deegan
2010-02-23 10:51 ` Devdutt Patnaik
2010-02-23 10:59 ` Keir Fraser
2010-02-23 11:05 ` Devdutt Patnaik
2010-02-23 11:10 ` Keir Fraser
2010-02-23 17:05 ` Ian Jackson
2010-02-24 9:31 ` Ashish Bijlani
2010-02-24 11:01 ` Keir Fraser
2010-02-26 9:52 ` Tim Deegan
2010-02-26 10:27 ` Jan Beulich
2010-02-26 14:22 ` Tim Deegan
2010-02-26 14:48 ` Keir Fraser
2010-02-26 14:49 ` Jan Beulich [this message]
2010-02-26 15:29 ` Keir Fraser
2010-02-26 6:12 ` Xu, Jiajun
2010-02-26 8:38 ` Pasi Kärkkäinen
2010-02-26 8:39 ` Jan Beulich
2010-02-23 10:54 ` Jan Beulich
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=4B87ED950200007800031879@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=Tim.Deegan@citrix.com \
--cc=ashish.bijlani@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).