From: Pavel Begunkov <asml.silence@gmail.com>
To: "Zhang, Qiang" <Qiang.Zhang@windriver.com>,
Hillf Danton <hdanton@sina.com>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "syzbot+6cb11ade52aa17095297@syzkaller.appspotmail.com"
<syzbot+6cb11ade52aa17095297@syzkaller.appspotmail.com>,
"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 回复: [PATCH] io-wq: Fix UAF when wakeup wqe in hash waitqueue
Date: Mon, 24 May 2021 11:18:54 +0100 [thread overview]
Message-ID: <900206b7-cf22-8248-1130-89c8f9d5539b@gmail.com> (raw)
In-Reply-To: <DM6PR11MB4202B442C4C27740B6EE2D64FF269@DM6PR11MB4202.namprd11.prod.outlook.com>
On 5/24/21 10:19 AM, Zhang, Qiang wrote:
> On Mon, 24 May 2021 15:18:44 +0800
>> From: Zqiang <qiang.zhang@windriver.com>
>>
>> The syzbot report a UAF when iou-wrk accessing wqe of the hash
>> waitqueue. in the case of sharing a hash waitqueue between two
>> io-wq, when one of the io-wq is destroyed, all iou-wrk in this
>> io-wq are awakened, all wqe belonging to this io-wq are removed
>> from hash waitqueue, after that, all iou-wrk belonging to this
>> io-wq begin running, suppose following scenarios, wqe[0] and wqe[1]
>> belong to this io-wq, and these work has same hash value.
Zhang, btw check your mail encoding, should some plain unicode
--
Pavel Begunkov
prev parent reply other threads:[~2021-05-24 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 7:18 [PATCH] io-wq: Fix UAF when wakeup wqe in hash waitqueue qiang.zhang
[not found] ` <20210524082536.2032-1-hdanton@sina.com>
2021-05-24 9:19 ` 回复: " Zhang, Qiang
2021-05-24 10:16 ` Pavel Begunkov
2021-05-25 2:01 ` 回复: " Zhang, Qiang
2021-06-07 17:38 ` Pavel Begunkov
2021-06-10 1:49 ` Zhang, Qiang
2021-05-24 10:18 ` 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 \
--in-reply-to=900206b7-cf22-8248-1130-89c8f9d5539b@gmail.com \
--to=asml.silence@gmail.com \
--cc=Qiang.Zhang@windriver.com \
--cc=axboe@kernel.dk \
--cc=hdanton@sina.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+6cb11ade52aa17095297@syzkaller.appspotmail.com \
/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;
as well as URLs for NNTP newsgroup(s).