All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: "Graham, Simon" <Simon.Graham@stratus.com>,
	Keir Fraser <keir@xensource.com>,
	xen-devel@lists.xensource.com
Subject: Re: DomU crash during migration when suspendingsource domain
Date: Wed, 14 Feb 2007 15:43:02 +0000	[thread overview]
Message-ID: <C1F8DE86.967E%keir@xensource.com> (raw)
In-Reply-To: <342BAC0A5467384983B586A6B0B3767104A6A878@EXNA.corp.stratus.com>

On 14/2/07 15:08, "Graham, Simon" <Simon.Graham@stratus.com> wrote:

> Let me try that out here and get back to you -- I can submit a patch
> with this specific fix in if it solves the problem.
> 
> Since, as you say, this is just one aspect of dealing with hot plugging
> completely different processors, I somehow feel that a point fix like
> this wouldn't be accepted upstream and instead we'd need to think about
> a more complete solution (If, indeed, this is feasible).

Possibly true. In fact I think if you fix that function then you're going to
die in kobject_unregister() instead. The loop cache_remove_dev() is simply
bogus in your case since num_cache_leaves cannot be trusted.

A broader set of fixes might get accepted upstream because cache_add_dev()
can fail for other reasons too (at least out-of-memory) and any such failure
will cause cache_remove_dev() to barf. But it's not such a simple thing to
fix and it does not solve the general problem for us.

 -- Keir

  reply	other threads:[~2007-02-14 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 15:08 DomU crash during migration when suspendingsource domain Graham, Simon
2007-02-14 15:43 ` Keir Fraser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-14 14:43 Graham, Simon
2007-02-14 14:56 ` Keir Fraser
2007-02-14 15:15 ` Petersson, Mats
2007-02-14 13:57 Graham, Simon
2007-02-14 14:35 ` Keir Fraser

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=C1F8DE86.967E%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=Simon.Graham@stratus.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.