From: Tuguoyi <tu.guoyi@h3c.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, Fam Zheng <fam@euphon.net>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: Wangyongqing <w_yongqing@h3c.com>, Wangyong <wang.yongD@h3c.com>,
Changlimin <changlimin@h3c.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Chengchiwen <chengchiwen@h3c.com>
Subject: util/async: File descriptor leak in aio_context_unref()?
Date: Sun, 19 Jan 2020 08:14:51 +0000 [thread overview]
Message-ID: <c24d031088d5439d99e4b0b915f2e405@h3c.com> (raw)
In aio_context_new(), the @notifier variable will be initialized, but it
don't get cleaned up in aio_context_unref() when reference count reaches
to 0, it will cause file descriptor leak.
--
Best regards,
Guoyi
next reply other threads:[~2020-01-19 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 8:14 Tuguoyi [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-19 8:57 util/async: File descriptor leak in aio_context_unref()? Tuguoyi
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=c24d031088d5439d99e4b0b915f2e405@h3c.com \
--to=tu.guoyi@h3c.com \
--cc=changlimin@h3c.com \
--cc=chengchiwen@h3c.com \
--cc=fam@euphon.net \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=w_yongqing@h3c.com \
--cc=wang.yongD@h3c.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).