From: Nam Cao <namcao@linutronix.de>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Shuah Khan <shuah@kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Soheil Hassas Yeganeh <soheil@google.com>,
Khazhismel Kumykov <khazhy@google.com>,
Willem de Bruijn <willemb@google.com>,
Eric Dumazet <edumazet@google.com>, Jens Axboe <axboe@kernel.dk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Cc: Nam Cao <namcao@linutronix.de>
Subject: [PATCH 0/2] eventpoll: Fix epoll_wait() report false negative
Date: Fri, 18 Jul 2025 09:52:27 +0200 [thread overview]
Message-ID: <cover.1752824628.git.namcao@linutronix.de> (raw)
Hi,
While staring at epoll, I noticed ep_events_available() looks wrong. I
wrote a small program to confirm, and yes it is definitely wrong.
This series adds a reproducer to kselftest, and fix the bug.
Nam Cao (2):
selftests/eventpoll: Add test for multiple waiters
eventpoll: Fix epoll_wait() report false negative
fs/eventpoll.c | 16 +------
.../filesystems/epoll/epoll_wakeup_test.c | 45 +++++++++++++++++++
2 files changed, 47 insertions(+), 14 deletions(-)
--
2.39.5
next reply other threads:[~2025-07-18 7:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 7:52 Nam Cao [this message]
2025-07-18 7:52 ` [PATCH 1/2] selftests/eventpoll: Add test for multiple waiters Nam Cao
2025-07-18 7:52 ` [PATCH 2/2] eventpoll: Fix epoll_wait() report false negative Nam Cao
2025-07-18 8:38 ` Soheil Hassas Yeganeh
2025-07-18 8:59 ` Nam Cao
2026-04-29 6:54 ` Christian Brauner
2026-04-29 7:27 ` Nam Cao
2026-04-29 15:34 ` Mateusz Guzik
2026-05-03 13:24 ` Nam Cao
2026-05-04 12:00 ` David Laight
2025-09-17 12:49 ` Mateusz Guzik
2025-09-17 13:41 ` Nam Cao
2025-09-17 16:05 ` Mateusz Guzik
2025-09-17 16:08 ` Mateusz Guzik
2025-09-17 18:03 ` Khazhy Kumykov
2025-09-17 22:28 ` Khazhy Kumykov
2025-09-17 22:38 ` Mateusz Guzik
2025-09-22 6:26 ` Nam Cao
2025-09-20 14:42 ` David Laight
2025-09-20 14:45 ` Mateusz Guzik
2025-09-17 7:27 ` [PATCH 0/2] " Nam Cao
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=cover.1752824628.git.namcao@linutronix.de \
--to=namcao@linutronix.de \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=dave@stgolabs.net \
--cc=edumazet@google.com \
--cc=jack@suse.cz \
--cc=khazhy@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=soheil@google.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.