[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <49564120-813d-2b80-94be-bde8123809a9@oracle.com>
Date: Mon, 18 Feb 2019 16:04:14 +0800
From: Dongli Zhang <dongli.zhang@...cle.com>
To: Konrad Rzeszutek Wilk <konrad@...nok.org>, konrad.wilk@...cle.com
Cc: Roger Pau Monné <roger.pau@...rix.com>,
xen-devel@...ts.xenproject.org, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, axboe@...nel.dk,
Paul.Durrant@...rix.com
Subject: Re: [Xen-devel] [PATCH v6 2/2] xen/blkback: rework connect_ring() to
avoid inconsistent xenstore 'ring-page-order' set by malicious blkfront
Hi Konrad,
On 1/17/19 11:29 PM, Konrad Rzeszutek Wilk wrote:
> On Tue, Jan 15, 2019 at 09:20:36AM +0100, Roger Pau Monné wrote:
>> On Tue, Jan 15, 2019 at 12:41:44AM +0800, Dongli Zhang wrote:
>>> The xenstore 'ring-page-order' is used globally for each blkback queue and
>>> therefore should be read from xenstore only once. However, it is obtained
>>> in read_per_ring_refs() which might be called multiple times during the
>>> initialization of each blkback queue.
>>>
>>> If the blkfront is malicious and the 'ring-page-order' is set in different
>>> value by blkfront every time before blkback reads it, this may end up at
>>> the "WARN_ON(i != (XEN_BLKIF_REQS_PER_PAGE * blkif->nr_ring_pages));" in
>>> xen_blkif_disconnect() when frontend is destroyed.
>>>
>>> This patch reworks connect_ring() to read xenstore 'ring-page-order' only
>>> once.
>>>
>>> Signed-off-by: Dongli Zhang <dongli.zhang@...cle.com>
>>
>> LGTM:
>>
>> Reviewed-by: Roger Pau Monné <roger.pau@...rix.com>
>
> Applied.
>
> Will push out to Jens in a couple of days. Thank you!
>>
>> Thanks!
I only see the PATCH 1/2 (xen/blkback: add stack variable 'blkif' in
connect_ring()) on the top of below branch for Jens, would you please apply this
one (PATCH 2/2) as well?
https://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git/log/?h=linux-next
1/2 is only a prerequisite for 2/2.
Thank you very much!
Dongli Zhang
Powered by blists - more mailing lists