public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Hao Xu <[email protected]>, Jens Axboe <[email protected]>,
	[email protected]
Subject: Re: [PATCH v2 0/4] rsrc quiesce fixes/hardening v2
Date: Mon, 22 Feb 2021 14:05:08 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 21/02/2021 13:22, Hao Xu wrote:
> 在 2021/2/21 上午2:03, Pavel Begunkov 写道:
>> v2: concurrent quiesce avoidance (Hao)
>>      resurrect-release patch
>>
>> Pavel Begunkov (4):
>>    io_uring: zero ref_node after killing it
>>    io_uring: fix io_rsrc_ref_quiesce races
>>    io_uring: keep generic rsrc infra generic
>>    io_uring: wait potential ->release() on resurrect
>>
>>   fs/io_uring.c | 96 ++++++++++++++++++++++++---------------------------
>>   1 file changed, 45 insertions(+), 51 deletions(-)
>>
> I tested this patchset with the same tests
> for "io_uring: don't hold uring_lock ..."
> 
> Tested-by: Hao Xu <[email protected]>

Great, thanks

FYI, looks like your emails have a strange encoding. It's
readable, but at least for me shows "undefined encoding".

-- 
Pavel Begunkov

      reply	other threads:[~2021-02-22 14:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 18:03 [PATCH v2 0/4] rsrc quiesce fixes/hardening v2 Pavel Begunkov
2021-02-20 18:03 ` [PATCH v2 1/4] io_uring: zero ref_node after killing it Pavel Begunkov
2021-02-20 18:03 ` [PATCH v2 2/4] io_uring: fix io_rsrc_ref_quiesce races Pavel Begunkov
2021-02-20 18:03 ` [PATCH v2 3/4] io_uring: keep generic rsrc infra generic Pavel Begunkov
2021-02-20 18:03 ` [PATCH v2 4/4] io_uring: wait potential ->release() on resurrect Pavel Begunkov
2021-02-20 18:33 ` [PATCH v2 0/4] rsrc quiesce fixes/hardening v2 Jens Axboe
2021-02-21 13:22 ` Hao Xu
2021-02-22 14:05   ` 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] \
    [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