From: Eric Wong <e@80x24.org>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Arnd Bergmann <arnd@arndb.de>, Al Viro <viro@zeniv.linux.org.uk>,
Jason Baron <jbaron@akamai.com>,
linux-kernel@vger.kernel.org, Omar Kilani <omar.kilani@gmail.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: Strange issues with epoll since 5.0
Date: Wed, 1 May 2019 07:39:06 +0000 [thread overview]
Message-ID: <20190501073906.ekqr7xbw3qkfgv56@dcvr> (raw)
In-Reply-To: <20190501021405.hfvd7ps623liu25i@dcvr>
Eric Wong <e@80x24.org> wrote:
> (didn't test AIO, but everything else seems good)
"seems" != "is"
Now that I understand the fix for epoll, the fs/select.c changes
would hit the same problem and not return -EINTR when it should.
I'll let you guys decide how to fix this, but there's definitely
a problem when "(errno == EINTR)" comparisons in userspace
stop working.
next prev parent reply other threads:[~2019-05-01 7:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+8F9hicnF=kvjXPZFQy=Pa2HJUS3JS+G9VswFHNQQynPMHGVQ@mail.gmail.com>
[not found] ` <20190424193903.swlfmfuo6cqnpkwa@dcvr>
2019-04-27 9:33 ` Strange issues with epoll since 5.0 Eric Wong
2019-04-27 23:31 ` Deepa Dinamani
2019-04-28 0:48 ` Eric Wong
2019-04-29 20:47 ` Davidlohr Bueso
2019-04-29 21:04 ` Eric Wong
2019-04-30 21:07 ` Deepa Dinamani
2019-05-01 2:14 ` Eric Wong
2019-05-01 2:26 ` Eric Wong
2019-05-01 7:39 ` Eric Wong [this message]
2019-05-01 18:37 ` Deepa Dinamani
2019-05-01 20:48 ` Eric Wong
2019-05-01 20:53 ` Deepa Dinamani
2019-05-03 0:01 ` Deepa Dinamani
2019-05-03 2:34 ` Eric Wong
2019-05-03 3:34 ` Davidlohr Bueso
2019-05-03 3:42 ` [PATCH] signal: Adjust error codes according to restore_user_sigmask() Deepa Dinamani
2019-05-03 6:34 ` Eric Wong
2019-05-03 18:21 ` Deepa Dinamani
2019-05-03 19:51 ` Davidlohr Bueso
2019-05-03 22:53 ` Deepa Dinamani
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=20190501073906.ekqr7xbw3qkfgv56@dcvr \
--to=e@80x24.org \
--cc=arnd@arndb.de \
--cc=dave@stgolabs.net \
--cc=deepa.kernel@gmail.com \
--cc=jbaron@akamai.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=omar.kilani@gmail.com \
--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).