From: Peter Xu <peterx@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Jie Wang <wangjie88@huawei.com>,
stefanha@redhat.com, eblake@redhat.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org, eric.fangyi@huawei.com,
wu.wubin@huawei.com
Subject: Re: [Qemu-devel] [PATCH] iothread: fix epollfd leak in the process of delIOThread
Date: Wed, 16 May 2018 11:11:37 +0800 [thread overview]
Message-ID: <20180516031137.GE9089@xz-mi> (raw)
In-Reply-To: <20180516013831.GC6731@lemon.usersys.redhat.com>
On Wed, May 16, 2018 at 09:38:31AM +0800, Fam Zheng wrote:
> On Tue, 05/15 20:00, Jie Wang wrote:
> > When we call addIOThread, the epollfd created in aio_context_setup,
> > but not close it in the process of delIOThread, so the epollfd will leak.
> >
> > Signed-off-by: Jie Wang <wangjie88@huawei.com>
> > ---
> > iothread.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/iothread.c b/iothread.c
> > index aff1281..23ac0a8 100644
> > --- a/iothread.c
> > +++ b/iothread.c
> > @@ -128,6 +128,7 @@ static void iothread_instance_finalize(Object *obj)
> > * GSources first before destroying any GMainContext.
> > */
> > if (iothread->ctx) {
> > + close(iothread->ctx->epollfd);
> > aio_context_unref(iothread->ctx);
> > iothread->ctx = NULL;
> > }
> > --
> > 1.8.3.1
> >
>
> Please add an aio_context_destroy() function in aio-posix.c and call it from
> aio_context_finalize(). IOThread code should not touch AioContext internals.
I believe Fam means aio_ctx_finalize().
> Also please remember to wrap the close() code in CONFIG_EPOLL_CREATE1. An empty
> function may need to be added to aio-win32.c, too.
Agreed.
--
Peter Xu
prev parent reply other threads:[~2018-05-16 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 12:00 [Qemu-devel] [PATCH] iothread: fix epollfd leak in the process of delIOThread Jie Wang
2018-05-16 1:38 ` Fam Zheng
2018-05-16 3:11 ` Peter Xu [this message]
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=20180516031137.GE9089@xz-mi \
--to=peterx@redhat.com \
--cc=eblake@redhat.com \
--cc=eric.fangyi@huawei.com \
--cc=famz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wangjie88@huawei.com \
--cc=wu.wubin@huawei.com \
/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).