From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [Xen-users] "xl restore" leaks a file descriptor? Date: Wed, 12 Aug 2015 10:30:35 +0100 Message-ID: <1439371835.9747.324.camel@citrix.com> References: <1438592915.30740.101.camel@citrix.com> <1439283311.9747.193.camel@citrix.com> <1439308093.9747.291.camel@citrix.com> <20150811170725.GU7460@zion.uk.xensource.com> <1439368873.9747.302.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1439368873.9747.302.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: xen-devel , Andrew Armenia , Ian Jackson , xen-users@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org On Wed, 2015-08-12 at 09:41 +0100, Ian Campbell wrote: > On Tue, 2015-08-11 at 18:07 +0100, Wei Liu wrote: > > > > I don't see how CLOEXEC would be of any use if xl doesn't actually exec > > anything. > > Duh, for some reason I thought daemonize would activate the CLOEXEC, but > it's just fork without exec. Silly me. FWIW I did manage to confirm that libxl isn't messing up the CLOEXEC state of the FD, it correctly only clears it between the fork and exec when spawning the save restore helper. Any messing which libxc does is safely contained in that subprocess. Ian.