From: Al Viro <viro@zeniv.linux.org.uk>
To: Sergey Nikitin <nikitins@oktetlabs.ru>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: PROBLEM: epoll_wait() does not return events when running in multiple threads
Date: Thu, 10 Sep 2020 12:54:58 +0100 [thread overview]
Message-ID: <20200910115458.GZ1236603@ZenIV.linux.org.uk> (raw)
In-Reply-To: <8076083c-0ae3-9cef-6238-9a651b026ade@oktetlabs.ru>
On Thu, Sep 10, 2020 at 12:48:34PM +0300, Sergey Nikitin wrote:
> Hi!
>
> epoll does not report an event to all the threads running epoll_wait() on
> the same epoll descriptor.
> The behavior appeared in recent kernel versions starting with 5.6 probably.
>
> How to reproduce:
> - create a pair of sockets
> - create epoll instance
> - register the socket on the epoll instance, listen for EPOLLIN events
> - start 2 threads running epoll_wait()
> - send some data to the socket
> - see that epoll_wait() within one of the threads reported an event, unlike
> another.
Could you reproduce it on mainline kernel and try to bisect it?
next prev parent reply other threads:[~2020-09-10 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 9:48 PROBLEM: epoll_wait() does not return events when running in multiple threads Sergey Nikitin
2020-09-10 11:54 ` Al Viro [this message]
2020-09-14 15:35 ` Sergey Nikitin
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=20200910115458.GZ1236603@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nikitins@oktetlabs.ru \
/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).