From: Jens Axboe <[email protected]>
To: Andres Freund <[email protected]>
Cc: [email protected]
Subject: Re: io_uring_enter() returns EAGAIN after child exit in 5.12
Date: Wed, 24 Feb 2021 09:24:06 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2/23/21 9:54 PM, Andres Freund wrote:
> Hi,
>
> On 2021-02-23 21:33:38 -0700, Jens Axboe wrote:
>> On 2/23/21 9:31 PM, Andres Freund wrote:
>>> Jens, seems like it'd make sense to apply the test case upthread into
>>> the liburing repo. Do you want me to open a PR?
>>
>> I think so, it's a good addition. Either a PR or just an emailed patch,
>> whatever you prefer. Well, the previous email had whitespace damage,
>> so maybe a PR is safer :-)
>
> Done https://github.com/axboe/liburing/pull/306. The damage originated
> from me foolishly just copy-pasting it from the terminal :) - I wrote it
> a test VM and was too lazy to copy the diff out...
I totally sympathize with that :-)
I've merged your pull request, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-02-24 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 3:25 io_uring_enter() returns EAGAIN after child exit in 5.12 Andres Freund
2021-02-24 3:35 ` Jens Axboe
2021-02-24 4:31 ` Andres Freund
2021-02-24 4:33 ` Jens Axboe
2021-02-24 4:54 ` Andres Freund
2021-02-24 16:24 ` 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] \
/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