From: Roman Penyaev <rpenyaev@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jason Baron <jbaron@akamai.com>,
Khazhismel Kumykov <khazhy@google.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/1] epoll: call final ep_events_available() check under the lock
Date: Tue, 05 May 2020 22:58:01 +0200 [thread overview]
Message-ID: <35b7d79b5cc7ee5befb1e632043701a7@suse.de> (raw)
In-Reply-To: <20200505130357.04566dee5501c3787105376f@linux-foundation.org>
On 2020-05-05 22:03, Andrew Morton wrote:
> On Tue, 05 May 2020 10:42:05 +0200 Roman Penyaev <rpenyaev@suse.de>
> wrote:
>
>> May I ask you to remove "epoll: ensure ep_poll() doesn't miss wakeup
>> events" from your -mm queue? Jason lately found out that the patch
>> does not fully solve the problem and this one patch is a second
>> attempt to do things correctly in a different way (namely to do
>> the final check under the lock). Previous changes are not needed.
>
> Where do we stand with Khazhismel's "eventpoll: fix missing wakeup for
> ovflist in ep_poll_callback"?
>
> http://lkml.kernel.org/r/20200424190039.192373-1-khazhy@google.com
This one from Khazhismel is needed. Others are complementary to the
Khazhismel's, except the "epoll: ensure ep_poll() doesn't miss
wakeup events", which you've already removed.
Thanks.
--
Roman
next prev parent reply other threads:[~2020-05-05 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 8:40 [PATCH 1/1] epoll: call final ep_events_available() check under the lock Roman Penyaev
2020-05-05 8:42 ` Roman Penyaev
2020-05-05 20:03 ` Andrew Morton
2020-05-05 20:35 ` Khazhismel Kumykov
2020-05-05 20:58 ` Roman Penyaev [this message]
2020-05-05 14:30 ` Jason Baron
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=35b7d79b5cc7ee5befb1e632043701a7@suse.de \
--to=rpenyaev@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jbaron@akamai.com \
--cc=khazhy@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).