From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH for-next] io_uring: fix io_timeout_remove locking
Date: Wed, 18 Aug 2021 07:25:56 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <d6f03d653a4d7bf693ef6f39b6a426b6d97fd96f.1629280204.git.asml.silence@gmail.com>
On 8/18/21 3:50 AM, Pavel Begunkov wrote:
> io_timeout_cancel() posts CQEs so needs ->completion_lock to be held,
> so grab it in io_timeout_remove().
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-08-18 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 9:50 [PATCH for-next] io_uring: fix io_timeout_remove locking Pavel Begunkov
2021-08-18 13:25 ` 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