WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] tools/xl: only use the special "--incoming" name

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] tools/xl: only use the special "--incoming" name on actual migration
From: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Date: Wed, 24 Nov 2010 09:52:29 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 24 Nov 2010 01:53:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19692.5904.185300.135231@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <17d93860b47414fc7fbe.1290421022@xxxxxxxxxxxxxxxxxxxxxxx> <19692.5904.185300.135231@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
At 19:33 +0000 on 23 Nov (1290540816), Ian Jackson wrote:
> Tim Deegan writes ("[Xen-devel] [PATCH] tools/xl: only use the special 
> "--incoming" name on actual migration"):
> > tools/xl: only use the special "--incoming" name on actual migration
> > and not on every susequent reboot.
> 
> Well spotted.  However, doesn't this:
> 
> > +                            d_config.c_info.name = strdup(common_domname);
> 
> leak the old value of c_info.name ? 

In the case where this happens, the old name has been passed by
reference up the stack to the calling function, but in this path (the
child of a fork) we never return to the caller.  So, er, maybe?

Tim.

-- 
Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>