From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: Re: [PATCH liburing] test/lfs-open: less limited test_drained_files
Date: Tue, 20 Oct 2020 17:15:39 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 20/10/2020 15:12, Jens Axboe wrote:
> On 10/19/20 9:46 AM, Pavel Begunkov wrote:
>> close(dup(io_uring)) should not neccessary cancel all requests with
>> files, because files are not yet going away. Test that it doesn't hang
>> after close() and exits, that's enough.
>
> Applied with the below incremental.
Thanks! My gcc 9 didn't warn me for some reason.
--
Pavel Begunkov
prev parent reply other threads:[~2020-10-20 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 15:46 [PATCH liburing] test/lfs-open: less limited test_drained_files Pavel Begunkov
2020-10-20 14:12 ` Jens Axboe
2020-10-20 16:15 ` Pavel Begunkov [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