On Wed, 05/16 19:43, Peter Xu wrote:
> On Wed, May 16, 2018 at 07:14:53PM +0800, WangJie (Pluto) wrote:
> > Hi, Peter Xu:
> > If call aio_epoll_disable() here, aio_epoll_disable() will return
> > before close ctx->epollfd,
> > Because the ctx->epoll_enabled is false in the moment.
> >
I agree, wait for a reply from Fam
On 2018/5/16 19:43, Peter Xu wrote:
> On Wed, May 16, 2018 at 07:14:53PM +0800, WangJie (Pluto) wrote:
>> Hi, Peter Xu:
>> If call aio_epoll_disable() here, aio_epoll_disable() will return
>> before close ctx->epollfd,
>> Because the ctx->epoll_enabled
On Wed, May 16, 2018 at 07:14:53PM +0800, WangJie (Pluto) wrote:
> Hi, Peter Xu:
> If call aio_epoll_disable() here, aio_epoll_disable() will return
> before close ctx->epollfd,
> Because the ctx->epoll_enabled is false in the moment.
> In the process of addIOThread, aio_context_se
Hi, Peter Xu:
If call aio_epoll_disable() in aio_context_destroy, aio_epoll_disable()
will return before close(ctx->epollfd),
Because the ctx->epoll_enabled is false in the moment.
In the process of addIOThread, aio_context_setup created epoll without
call aio_epoll_try_enable
Hi, Peter Xu:
If call aio_epoll_disable() here, aio_epoll_disable() will return
before close ctx->epollfd,
Because the ctx->epoll_enabled is false in the moment.
In the process of addIOThread, aio_context_setup created epoll without
call aio_epoll_try_enable,
so ctx->epoll
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
---
include/block/aio.h | 8
util/aio-posix.c| 9 +
util/aio-win32.c| 4
util/async.c| 1 +
