From: Ian Jackson <ian.jackson@eu.citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>,
David Scott <dave@recoil.org>
Subject: Re: xenstored memory leak
Date: Wed, 13 Jul 2016 14:20:28 +0100 [thread overview]
Message-ID: <22406.16412.746116.997430@mariner.uk.xensource.com> (raw)
In-Reply-To: <20160713130740.GF31770@citrix.com>
Wei Liu writes ("Re: [Xen-devel] xenstored memory leak"):
> On Wed, Jul 13, 2016 at 02:21:38PM +0200, Juergen Gross wrote:
> > qemu as the device model is setting up a xenstore watch for each backend
> > type it is supporting. Unfortunately those watches are never removed
> > again. This sums up to the observed memory leak.
I think this must be a bug in C xenstored.
> > I'm not sure how oxenstored is avoiding the problem, may be by testing
> > socket connections to be still alive and so detecting qemu has gone.
> > OTOH this won't help for oxenstored running in another domain than the
> > device model (either due to oxenstore-stubdom, or a driver domain with
> > a qemu based device model).
>
> How unfortunate.
>
> My gut feeling is that xenstored shouldn't have the knowledge to
> associate a watch with a "process".
xenstored needs to associate watches with connections. If a
connection is terminated, the watches need to be cleaned up, along
with whatever other things "belong" to that connection (notably
transactions, and replies in flight).
Here a `connection' might be a socket, or a ring.
C xenstored does have code which tries to do this. It's a bit
impenetrable, though, because it's done through destructors provided
to the reference counting membery allocator (!)
> The concept of a process is only meaningful to OS, which wouldn't
> work on cross-domain xenstored setup. Maybe the OS xenbus driver
> should reap all watches on behalf the dead process. This would also
> avoid a crashed QEMU leaking resources.
The OS xenbus driver needs to mediate everything, so that it can
direct replies to the right places etc. It needs to (and does)
maintain a list of watches. When a process closes the xenbus device,
it destroys the watches by issuing commands to the actual xenstored
via its ring connection.
I guess that the qemu in this case is making a socket connection to
xenstored.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-13 13:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 7:31 xenstored memory leak Juergen Gross
2016-07-06 13:48 ` Andrew Cooper
2016-07-06 13:55 ` Juergen Gross
2016-07-06 13:59 ` Andrew Cooper
2016-07-07 16:22 ` Wei Liu
2016-07-13 12:21 ` Juergen Gross
2016-07-13 12:40 ` Andrew Cooper
2016-07-13 13:21 ` Juergen Gross
2016-07-13 13:30 ` Ian Jackson
2016-07-13 13:07 ` Wei Liu
2016-07-13 13:17 ` David Vrabel
2016-07-13 13:32 ` Juergen Gross
2016-07-13 13:37 ` David Vrabel
2016-07-13 14:28 ` Ian Jackson
2016-07-13 14:50 ` Juergen Gross
2016-07-13 13:20 ` Ian Jackson [this message]
2016-07-13 13:47 ` Wei Liu
2016-07-13 13:25 ` Juergen Gross
2016-07-13 13:52 ` Wei Liu
2016-07-13 14:09 ` Juergen Gross
2016-07-13 14:18 ` Wei Liu
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=22406.16412.746116.997430@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=dave@recoil.org \
--cc=jgross@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).