From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: [PATCH 1/1] io_uring: fix assign file locking issues
Date: Tue, 12 Apr 2022 08:39:53 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <0d9b9f37841645518503f6a207e509d14a286aba.1649773463.git.asml.silence@gmail.com>
On Tue, 12 Apr 2022 15:24:43 +0100, Pavel Begunkov wrote:
> io-wq work cancellation path can't take uring_lock as how it's done on
> file assignment, we have to handle IO_WQ_WORK_CANCEL first, this fixes
> encountered hangs.
>
>
Applied, thanks!
[1/1] io_uring: fix assign file locking issues
commit: 0f8da75b51ac863b9435368bd50691718cc454b0
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-04-12 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 14:24 [PATCH 1/1] io_uring: fix assign file locking issues Pavel Begunkov
2022-04-12 14:39 ` 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 \
--in-reply-to=164977439318.31918.13119052065490090284.b4-ty@kernel.dk \
[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