From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH 0/2] io_req_complete_post() fix
Date: Tue, 9 Mar 2021 08:01:02 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 3/8/21 5:37 PM, Pavel Begunkov wrote:
> May use more gazing by someone to avoid obvious/stupid mistakes
>
> Pavel Begunkov (2):
> io_uring: add io_disarm_next() helper
> io_uring: fix complete_post races for linked req
>
> fs/io_uring.c | 89 ++++++++++++++++++++++++++++-----------------------
> 1 file changed, 49 insertions(+), 40 deletions(-)
I looked through it and it looks good to me.
--
Jens Axboe
prev parent reply other threads:[~2021-03-09 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 0:37 [PATCH 0/2] io_req_complete_post() fix Pavel Begunkov
2021-03-09 0:37 ` [PATCH 1/2] io_uring: add io_disarm_next() helper Pavel Begunkov
2021-03-09 0:37 ` [PATCH 2/2] io_uring: fix complete_post races for linked req Pavel Begunkov
2021-03-09 15:01 ` 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