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/

Home

xen-devel

[Top] [All Lists]

Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks

from [Vincent Hanquez]

[Permanent Link][Original]

To:	"Gianni Tedesco (3P)" <gianni.tedesco@xxxxxxxxxx>
Subject:	Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks
From:	Vincent Hanquez <vincent.hanquez@xxxxxxxxxxxxx>
Date:	Tue, 3 Aug 2010 11:51:47 +0100
Cc:	Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Tue, 03 Aug 2010 03:52:28 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<1280830700.18490.82.camel@xxxxxxxxxxxxxxxxxxxxxx>
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:	<patchbomb.1280752270@xxxxxxxxxxxxxxxxxxxxx> <1280754703.18490.65.camel@xxxxxxxxxxxxxxxxxxxxxx> <4C56C60D.5060702@xxxxxxxxxxxxx> <1280757928.18490.72.camel@xxxxxxxxxxxxxxxxxxxxxx> <4C57CC53.7030107@xxxxxxxxxxxxx> <1280830700.18490.82.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100620 Icedove/3.0.5

On 03/08/10 11:18, Gianni Tedesco (3P) wrote:

I wasn't aware that was the original design. It's certainly not the case
right now.


it has unfortunately diverged in some calls indeed.

AFAICS that scheme would only guarantee everything has been freed if the
caller calls ctx_free() at appropriate points. If libxl were used in a
daemon, for example, it would not be simple to come up with a scheme
that guarantees memory bounds that are independent from uptime.


This scheme is already in place in the ocaml binding

--
Vincent

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

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Ian Campbell [Xen-devel] [PATCH 1 of 3] libxc: free thread specific hypercall buffer on xc_interface_close, Ian Campbell [Xen-devel] [PATCH 2 of 3] libxl: fix memory leak in libxl_name_to_domid, Ian Campbell [Xen-devel] [PATCH 3 of 3] xl: fix memory leaks in xl create, Ian Campbell Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Gianni Tedesco Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Vincent Hanquez Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Gianni Tedesco Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Vincent Hanquez Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Gianni Tedesco Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Vincent Hanquez <= Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Gianni Tedesco Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Vincent Hanquez Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Gianni Tedesco Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Ian Campbell Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Stefano Stabellini Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Stefano Stabellini

Previous by Date:	[Xen-devel] xl create error, Christoph Egger
Next by Date:	[Xen-devel] [PATCH 0 of 8] [RFC] libxl: autogenerate type definitions and destructor functions, Ian Campbell
Previous by Thread:	Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Gianni Tedesco
Next by Thread:	Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks, Gianni Tedesco
Indexes:	[Date] [Thread] [Top] [All Lists]

This site is hosted by Citrix