From: Jens Axboe <[email protected]>
To: yangerkun <[email protected]>,
Pavel Begunkov <[email protected]>,
[email protected]
Cc: Matthew Wilcox <[email protected]>,
Stefan Metzmacher <[email protected]>,
[email protected]
Subject: Re: [PATCH 5.12] io_uring: Convert personality_idr to XArray
Date: Sat, 13 Mar 2021 08:34:40 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 3/13/21 1:02 AM, yangerkun wrote:
>
>
> 在 2021/3/9 19:23, yangerkun 写道:
>>
>>
>> 在 2021/3/8 22:22, Pavel Begunkov 写道:
>>> On 08/03/2021 14:16, Pavel Begunkov wrote:
>>>> From: "Matthew Wilcox (Oracle)" <[email protected]>
>>>>
>>>> You can't call idr_remove() from within a idr_for_each() callback,
>>>> but you can call xa_erase() from an xa_for_each() loop, so switch the
>>>> entire personality_idr from the IDR to the XArray. This manifests as a
>>>> use-after-free as idr_for_each() attempts to walk the rest of the node
>>>> after removing the last entry from it.
>>>
>>> yangerkun, can you test it and similarly take care of buffer idr?
>>
>> Will try it latter :)
>
> Sorry for the latter reply. The patch pass the testcase.
>
> Besides, should we apply this patch first to deal with the same UAF for
> io_buffer_idr before convert to XArray?
>
> https://lore.kernel.org/io-uring/[email protected]/T/#u
Agree, and then defer an xarray conversion to 5.13. I'll take a look at
your patch and get it applied.
--
Jens Axboe
next prev parent reply other threads:[~2021-03-13 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 14:16 [PATCH 5.12] io_uring: Convert personality_idr to XArray Pavel Begunkov
2021-03-08 14:22 ` Pavel Begunkov
2021-03-08 16:16 ` Matthew Wilcox
2021-03-09 11:23 ` yangerkun
2021-03-13 8:02 ` yangerkun
2021-03-13 15:34 ` Jens Axboe [this message]
2021-03-13 19:01 ` Jens Axboe
2021-03-13 19:30 ` Jens Axboe
2021-03-13 19:54 ` Matthew Wilcox
2021-03-13 20:13 ` Jens Axboe
2021-03-13 20:22 ` Jens Axboe
2021-03-09 20:53 ` Jens Axboe
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] \
[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