From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH 5.13] io_uring: fortify tctx/io_wq cleanup
Date: Thu, 20 May 2021 07:55:34 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <827b021de17926fd807610b3e53a5a5fa8530856.1621513214.git.asml.silence@gmail.com>
On 5/20/21 6:21 AM, Pavel Begunkov wrote:
> We don't want anyone poking into tctx->io_wq awhile it's being destroyed
> by io_wq_put_and_exit(), and even though it shouldn't even happen, if
> buggy would be preferable to get a NULL-deref instead of subtle delayed
> failure or UAF.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-05-20 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 12:21 [PATCH 5.13] io_uring: fortify tctx/io_wq cleanup Pavel Begunkov
2021-05-20 13:55 ` 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