From: Jim Fehlig <jfehlig@suse.com>
To: Steve Prochniak <steve.prochniak@oracle.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
Ian Campbell <Ian.Campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: Xend FD leak upon migrate receive
Date: Tue, 07 May 2013 09:31:19 -0600 [thread overview]
Message-ID: <51891E47.1020606@suse.com> (raw)
In-Reply-To: <d061e328-9523-41ad-96dc-2d41aa959788@default>
Steve Prochniak wrote:
> Fyi - the leak occurs on the receiver side and only exists when using SSL migration. I don't know if that rings any bells or not.
>
Maybe op_quit() in tools/python/xen/xend/server/relocate.py needs to
handle cleaning up the pipe created in op_sslreceive()?
Regards,
Jim
> -----Original Message-----
> From: Ian Campbell [mailto:Ian.Campbell@citrix.com]
> Sent: Thursday, May 02, 2013 9:42 AM
> To: Sander Eikelenboom
> Cc: Steve Prochniak; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] Xend FD leak upon migrate receive
>
> On Thu, 2013-05-02 at 14:36 +0100, Sander Eikelenboom wrote:
>
>> Thursday, May 2, 2013, 1:42:11 PM, you wrote:
>>
>>
>>> On Wed, 2013-05-01 at 17:50 +0100, Steve Prochniak wrote:
>>>
>>>> Xend leaks one fd each time a guest migrates to it's server. I'm
>>>> wondering if this is a known problem with a known fix, or if someone
>>>> who knows that code better than me could point me in the right
>>>> direction.
>>>>
>>> I'm afraid xend is basically unmaintained these days (which has caused
>>> to become deprecated in current releases) AFAIK there aren't any people
>>> around who know the code in any great detail.
>>>
>>> I don't recall having heard of anything along the lines of what you
>>> report so I don't think it is a known problem.
>>>
>> Isn't this the same as the:
>> test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
>> test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check fail never pass
>>
>
> Why do you think that?
>
> AFAIK this is checking for leaked files (not file descriptors) and
> xenstore entries etc. Also it seems to pass for other test sequences
> which also involve xend and migration.
>
> Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
>
next prev parent reply other threads:[~2013-05-07 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 16:50 Xend FD leak upon migrate receive Steve Prochniak
2013-05-02 11:42 ` Ian Campbell
2013-05-02 13:36 ` Sander Eikelenboom
2013-05-02 13:42 ` Ian Campbell
2013-05-02 20:26 ` Steve Prochniak
2013-05-07 15:31 ` Jim Fehlig [this message]
2013-05-08 18:19 ` Steve Prochniak
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=51891E47.1020606@suse.com \
--to=jfehlig@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=linux@eikelenboom.it \
--cc=steve.prochniak@oracle.com \
--cc=xen-devel@lists.xen.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 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.