From: Eric Wong <e@80x24.org>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
omar.kilani@gmail.com, jbaron@akamai.com, arnd@arndb.de,
linux-fsdevel@vger.kernel.org, dave@stgolabs.net
Subject: Re: [PATCH] signal: Adjust error codes according to restore_user_sigmask()
Date: Fri, 3 May 2019 06:34:35 +0000 [thread overview]
Message-ID: <20190503063435.446aqcckbc6ri7xx@dcvr> (raw)
In-Reply-To: <20190503034205.12121-1-deepa.kernel@gmail.com>
Deepa Dinamani <deepa.kernel@gmail.com> wrote:
> Sorry, I was trying a new setup at work. I should have tested it.
> My bad, I've checked this one.
Thanks. This is good w.r.t. epoll_pwait and ppoll when applied
to 5.0.11 (no fs/io_uring.c).
Can't think of anything which uses pselect or aio on my system;
but it looks right to me.
> I've removed the questionable reported-by, since we're not sure if
> it is actually the same issue.
Yes, I hope Omar can test this, too.
Thanks again, all!
next prev parent reply other threads:[~2019-05-03 6:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 18:02 Strange issues with epoll since 5.0 Omar Kilani
2019-04-24 19:39 ` Eric Wong
2019-04-24 21:34 ` Davidlohr Bueso
2019-04-24 21:52 ` Davidlohr Bueso
2019-04-27 9:33 ` 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
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 [this message]
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=20190503063435.446aqcckbc6ri7xx@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).