From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>,
io-uring <[email protected]>
Subject: Re: [PATCH] io_uring: fix sporadic double CQE entry for close
Date: Fri, 31 Jan 2020 19:09:58 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 1/31/20 5:40 PM, Pavel Begunkov wrote:
> On 01/02/2020 03:21, Jens Axboe wrote:
>> We punt close to async for the final fput(), but we log the completion
>> even before that even in that case. We rely on the request not having
>> a files table assigned to detect what the final async close should do.
>> However, if we punt the async queue to __io_queue_sqe(), we'll get
>> ->files assigned and this makes io_close_finish() think it should both
>> close the filp again (which does no harm) AND log a new CQE event for
>> this request. This causes duplicate CQEs.
>>
>> Queue the request up for async manually so we don't grab files
>> needlessly and trigger this condition.
>>
>
> Evidently from your 2 last patches, it's becoming hard to track everything in
> the current state. As mentioned, I'm going to rework and fix submission and prep
> paths with a bit of formalisation.
Honestly don't think it's that bad, not unusual to have a bit of
fallout from the large amount of changes that just went in. That said,
I'm obviously always interested in anything that is clear and hardens
the flow.
--
Jens Axboe
prev parent reply other threads:[~2020-02-01 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 0:21 [PATCH] io_uring: fix sporadic double CQE entry for close Jens Axboe
2020-02-01 0:40 ` Pavel Begunkov
2020-02-01 2:09 ` 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