All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Smith <danms@us.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Xen Tools Developers <xen-tools@lists.xensource.com>,
	Xen Developers <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Make xend reject duplicates and rename zombies
Date: Thu, 15 Sep 2005 12:16:33 -0700	[thread overview]
Message-ID: <87mzmew38u.fsf@us.ibm.com> (raw)
In-Reply-To: <4329C366.2070006@us.ibm.com> (Anthony Liguori's message of "Thu, 15 Sep 2005 13:54:30 -0500")


AL> This patch renames the domain name which prevents a name class but
AL> does not solve the general problem.

I agree.  This is why in my original patch, I simply had the create
routine reject attempts to create domains with duplicate names.

Further, I will point out that what I meant by my comment attached to
this patch was not that it solved the general problem, but that it
seemed to make the problem not get in the way of some of my existing
tests :)

AL> I think the right solution is to make xm destroy not return until
AL> the domain has actually gone away and add a flag to xm destroy to
AL> return immediately if that behavior is ever desired.

Yep, I think that's a much better solution.  So, I think my original
patch should still be applied: xend should do its own checking for
duplicates, so that we don't rely on whatever tool is asking us to do
so.

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@us.ibm.com

  reply	other threads:[~2005-09-15 19:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15 15:49 [PATCH] Make xend reject duplicates and rename zombies Dan Smith
2005-09-15 18:54 ` Anthony Liguori
2005-09-15 19:16   ` Dan Smith [this message]
2005-09-16 14:45     ` Ted Kaczmarek
2005-09-16 19:52   ` [Xen-tools] " Christian Limpach
2005-09-16 21:37     ` Anthony Liguori
2005-09-16 21:48       ` Christian Limpach
2005-09-16 21:49         ` Anthony Liguori
2005-09-16 22:19           ` Christian Limpach

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=87mzmew38u.fsf@us.ibm.com \
    --to=danms@us.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-tools@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.