From: "yukuai (C)" <yukuai3@huawei.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: <axboe@kernel.dk>, <josef@toxicpanda.com>, <ming.lei@redhat.com>,
<linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<nbd@other.debian.org>, <yi.zhang@huawei.com>
Subject: Re: [PATCH v6 6/6] nbd: fix uaf in nbd_handle_reply()
Date: Wed, 15 Sep 2021 16:44:01 +0800 [thread overview]
Message-ID: <e933a436-52a7-2faa-63f9-3fa3f6eae610@huawei.com> (raw)
In-Reply-To: <YUGswNyMnFHxigsW@infradead.org>
On 2021/09/15 16:20, Christoph Hellwig wrote:
> On Wed, Sep 15, 2021 at 04:15:37PM +0800, Yu Kuai wrote:
>> +++ b/block/blk-core.c
>> @@ -489,6 +489,7 @@ void blk_queue_exit(struct request_queue *q)
>> {
>> percpu_ref_put(&q->q_usage_counter);
>> }
>> +EXPORT_SYMBOL(blk_queue_exit);
>
> These needs to be an EXPORT_SYMBOL_GPL. But more importantly it
> needs to be a separate properly documented patch, and this function
> needs to grow a kerneldoc comment as well.
>
>> + /*
>> + * Get q_usage_counter can prevent accessing freed request
>> + * through blk_mq_tag_to_rq() in nbd_handle_reply(). If
>> + * q_usage_counter is zero, then no request is inflight, which
>> + * means something is wrong since we expect to find a request to
>> + * complete here.
>> + */
>> + if (!percpu_ref_tryget(&q->q_usage_counter)) {
>> + dev_err(disk_to_dev(nbd->disk), "%s: no io inflight\n",
>> + __func__);
>> + break;
>> + }
>
> And this needs a properly documented wrapper as well.
>
>> +
>> cmd = nbd_handle_reply(nbd, args->index, &reply);
>> - if (IS_ERR(cmd))
>> + if (IS_ERR(cmd)) {
>> + blk_queue_exit(q);
>> break;
>> + }
>>
>> rq = blk_mq_rq_from_pdu(cmd);
>> if (likely(!blk_should_fake_timeout(rq->q)))
>> blk_mq_complete_request(rq);
>> + blk_queue_exit(q);
>
> That being said I can't say I like how this exposed block layer
> internals. We don't really need a reference to the queue here
> anywhere, you just use it as a dumb debug check. If we really want to
> reuse (abuse?) q_usage_counter a helper to just grab a reference and
> immediately drop it might be a better fit.
> .
Hi,
The uaf is because blk_mq_sched_free_requests() can concurrent with
nbd_read_stat(), and hold the ref during nbd_read_stat() can break the
concurrency, thus the ref can't be dropped immediately.
I'll use percpu_ref_put() directly as Ming suggestted.
Thanks,
Kuai
next prev parent reply other threads:[~2021-09-15 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 8:15 [PATCH v6 0/6] handle unexpected message from server Yu Kuai
2021-09-15 8:15 ` [PATCH v6 1/6] nbd: don't handle response without a corresponding request message Yu Kuai
2021-09-15 8:15 ` [PATCH v6 2/6] nbd: make sure request completion won't concurrent Yu Kuai
2021-09-15 8:15 ` [PATCH v6 3/6] nbd: check sock index in nbd_read_stat() Yu Kuai
2021-09-15 8:15 ` [PATCH v6 4/6] nbd: don't start request if nbd_queue_rq() failed Yu Kuai
2021-09-15 8:15 ` [PATCH v6 5/6] nbd: partition nbd_read_stat() into nbd_read_reply() and nbd_handle_reply() Yu Kuai
2021-09-15 8:15 ` [PATCH v6 6/6] nbd: fix uaf in nbd_handle_reply() Yu Kuai
2021-09-15 8:20 ` Christoph Hellwig
2021-09-15 8:44 ` yukuai (C) [this message]
2021-09-15 8:28 ` Ming Lei
2021-09-15 8:41 ` yukuai (C)
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=e933a436-52a7-2faa-63f9-3fa3f6eae610@huawei.com \
--to=yukuai3@huawei.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=nbd@other.debian.org \
--cc=yi.zhang@huawei.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