All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jim Fehlig <jfehlig@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: PATCH: Fix name  uniqueness check
Date: Thu, 27 Sep 2007 21:40:23 +0100	[thread overview]
Message-ID: <20070927204023.GQ17433@redhat.com> (raw)
In-Reply-To: <46FC0792.2040602@novell.com>

On Thu, Sep 27, 2007 at 01:42:10PM -0600, Jim Fehlig wrote:
> Daniel P. Berrange wrote:
> > On Thu, Sep 27, 2007 at 11:16:27AM -0600, Jim Fehlig wrote:
> >> Yes, I was not sure what this patch was attempting to fix either.  There
> >> was some discussion about the patch in this thread
> >>
> >> http://lists.xensource.com/archives/html/xen-devel/2007-05/msg00887.html
> >>     
> >
> > Ok, so if I follow that correctly, the crux of the issue is that it was 
> > possible to start 2 unmanaged domains with same name and same uuid. So
> > I think we can probably address that by checking for UUID, and the only
> > if both are running, also check for domid match. So really a combo of
> > both the original & current code.
> >   
> 
> Unstable, but not 3.1.1, also has
> 
>   http://xenbits2.xensource.com/xen-unstable.hg?rev/207582c8d88b
> 
> I did a little testing on a 3.1-based system that includes the above c/s
> and your reversion of c/s 15124.  No problems noticed testing create,
> new, reboot, save, restore.  Did not test migration or hvm guests.  So
> perhaps reverting 15124 is fine for unstable but not sure about 3.1.1
> *without* c/s 15642.

Yep, I just tested 3.1.1 with 15124 reverted, and 15642 applied and it copes
with the use cases I have. So I'd reckon on making those two changes to the
3.1-testing tree would be sufficient. 

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2007-09-27 20:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 16:50 PATCH: Fix name uniqueness check Daniel P. Berrange
2007-09-27 17:16 ` Jim Fehlig
2007-09-27 17:39   ` Daniel P. Berrange
2007-09-27 19:42     ` Jim Fehlig
2007-09-27 20:40       ` Daniel P. Berrange [this message]
2007-10-01  5:36         ` Keir Fraser
2007-10-01 13:57           ` Daniel P. Berrange
2007-10-01 18:18             ` Daniel P. Berrange
2007-10-01 22:12               ` Daniel P. Berrange
2007-10-02 13:11                 ` Masaki Kanno
2007-10-02 14:47                   ` Daniel P. Berrange
2007-10-05  5:19                     ` Masaki Kanno
2007-10-05 13:35                       ` Daniel P. Berrange
2007-10-05 14:26                         ` Masaki Kanno
2007-09-28  3:59 ` Masaki Kanno
2007-09-28  4:56   ` Masaki Kanno

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=20070927204023.GQ17433@redhat.com \
    --to=berrange@redhat.com \
    --cc=jfehlig@novell.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.