[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpeguDR4RqfNgaGSxSA9GKtFD7605pMo80fM4EEGV42bi80g@mail.gmail.com>
Date: Tue, 27 Jan 2026 11:37:41 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: Zhang Tianci <zhangtianci.1997@...edance.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Geng Xueyu <gengxueyu.520@...edance.com>, Wang Jian <wangjian.pg@...edance.com>,
Xie Yongji <xieyongji@...edance.com>
Subject: Re: [PATCH] fuse: fix the bug of missing EPOLLET event wakeup
On Thu, 25 Dec 2025 at 12:03, Zhang Tianci
<zhangtianci.1997@...edance.com> wrote:
>
> Users using Go have reported an issue to us:
> When performing read/write operations with goroutines,
> since fuse's file->f_ops->poll is not empty,
Another one of those historical mistakes...
> read/write operations are conducted via epoll.
> Additionally, goroutines use the EPOLLET wake-up mode.
>
> Currently, the implementation of fuse_file_poll has
> the following problem:
> After receiving EAGAIN during read/write operations,
Why is read/write returning EAGAIN?
Thanks,
Miklos
Powered by blists - more mailing lists