From: Fam Zheng <famz@redhat.com>
To: Jie Wang <wangjie88@huawei.com>
Cc: stefanha@redhat.com, peterx@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 v2] iothread: fix epollfd leak in the process of delIOThread
Date: Wed, 16 May 2018 17:07:34 +0800 [thread overview]
Message-ID: <20180516090734.GF6731@lemon.usersys.redhat.com> (raw)
In-Reply-To: <1526452784-45308-1-git-send-email-wangjie88@huawei.com>
On Wed, 05/16 14:39, Jie Wang wrote:
> From: w00251574 <wangjie88@huawei.com>
>
> 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>
> ---
> include/block/aio.h | 8 ++++++++
> util/aio-posix.c | 7 +++++++
> util/aio-win32.c | 4 ++++
> util/async.c | 1 +
> 4 files changed, 20 insertions(+)
>
> diff --git a/include/block/aio.h b/include/block/aio.h
> index a1d6b9e249..ae6f354e6c 100644
> --- a/include/block/aio.h
> +++ b/include/block/aio.h
> @@ -554,6 +554,14 @@ static inline bool in_aio_context_home_thread(AioContext *ctx)
> */
> void aio_context_setup(AioContext *ctx);
>
> +/**
> + * aio_context_destroy:
> + * @ctx: the aio context
> + *
> + * Destroy the aio context.
> + */
> +void aio_context_destroy(AioContext *ctx);
> +
> /**
> * aio_context_set_poll_params:
> * @ctx: the aio context
> diff --git a/util/aio-posix.c b/util/aio-posix.c
> index d8f0cb4af8..bd81455851 100644
> --- a/util/aio-posix.c
> +++ b/util/aio-posix.c
> @@ -713,6 +713,13 @@ void aio_context_setup(AioContext *ctx)
> #endif
> }
>
> +void aio_context_destroy(AioContext *ctx)
> +{
> +#ifdef CONFIG_EPOLL_CREATE1
> + close(ctx->epollfd);
In aio_context_setup, epoll_create1 could fail. Putting this inside an "if
(ctx->epllfd >= 0)" condition is cleaner, I think.
> +#endif
> +}
> +
> void aio_context_set_poll_params(AioContext *ctx, int64_t max_ns,
> int64_t grow, int64_t shrink, Error **errp)
> {
> diff --git a/util/aio-win32.c b/util/aio-win32.c
> index a67b00c6ad..e676a8d9b2 100644
> --- a/util/aio-win32.c
> +++ b/util/aio-win32.c
> @@ -407,6 +407,10 @@ void aio_context_setup(AioContext *ctx)
> {
> }
>
> +void aio_context_destroy(AioContext *ctx)
> +{
> +}
> +
> void aio_context_set_poll_params(AioContext *ctx, int64_t max_ns,
> int64_t grow, int64_t shrink, Error **errp)
> {
> diff --git a/util/async.c b/util/async.c
> index 4dd9d95a9e..03f62787f2 100644
> --- a/util/async.c
> +++ b/util/async.c
> @@ -298,6 +298,7 @@ aio_ctx_finalize(GSource *source)
> qemu_rec_mutex_destroy(&ctx->lock);
> qemu_lockcnt_destroy(&ctx->list_lock);
> timerlistgroup_deinit(&ctx->tlg);
> + aio_context_destroy(ctx);
> }
>
> static GSourceFuncs aio_source_funcs = {
> --
> 2.15.0.windows.1
>
next prev parent reply other threads:[~2018-05-16 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 6:39 [Qemu-devel] [PATCH v2] iothread: fix epollfd leak in the process of delIOThread Jie Wang
2018-05-16 9:07 ` Fam Zheng [this message]
2018-05-16 9:11 ` Peter Xu
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=20180516090734.GF6731@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=eblake@redhat.com \
--cc=eric.fangyi@huawei.com \
--cc=peterx@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).