From: Jens Axboe <[email protected]>
To: Andres Freund <[email protected]>
Cc: [email protected], Oleg Nesterov <[email protected]>
Subject: Re: signals not reliably interrupting io_uring_enter anymore
Date: Sat, 4 Jul 2020 13:45:41 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 7/4/20 1:11 PM, Andres Freund wrote:
> Hi,
>
> On 2020-07-04 08:55:39 -0600, Jens Axboe wrote:
>> This tests out fine for me, and it avoids TWA_SIGNAL if we're not using
>> an eventfd.
>
> I tried this variant and it does fix the problem for me, all my tests
> pass again. I assume this will eventually need to be in stable for 5.7?
Yeah, it should go in with the original, I'm aware of it and will keep
an eye on it.
Thanks for testing! Both this patch, but also the -rc series. So much
easier to catch incidents like this upfront.
--
Jens Axboe
prev parent reply other threads:[~2020-07-04 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 0:00 signals not reliably interrupting io_uring_enter anymore Andres Freund
2020-07-04 0:15 ` Andres Freund
2020-07-04 0:48 ` Jens Axboe
2020-07-04 1:13 ` Andres Freund
2020-07-04 1:52 ` Jens Axboe
2020-07-04 2:08 ` Jens Axboe
2020-07-04 2:56 ` Jens Axboe
2020-07-04 14:55 ` Jens Axboe
2020-07-04 19:11 ` Andres Freund
2020-07-04 19:45 ` Jens Axboe [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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