[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4595107c-64aa-5139-c86e-f5bff5b3d87d@citrix.com>
Date: Fri, 20 Dec 2019 10:26:09 +0000
From: Sergey Dyasli <sergey.dyasli@...rix.com>
To: Boris Ostrovsky <BORIS.OSTROVSKY@...CLE.COM>
CC: <xen-devel@...ts.xen.org>, <kasan-dev@...glegroups.com>,
<linux-kernel@...r.kernel.org>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Juergen Gross <jgross@...e.com>,
Stefano Stabellini <sstabellini@...nel.org>,
George Dunlap <george.dunlap@...rix.com>,
Ross Lagerwall <ross.lagerwall@...rix.com>,
"sergey.dyasli@...rix.com >> Sergey Dyasli"
<sergey.dyasli@...rix.com>
Subject: Re: [RFC PATCH 0/3] basic KASAN support for Xen PV domains
On 17/12/2019 18:06, Boris Ostrovsky wrote:
>
>
>> On Dec 17, 2019, at 9:08 AM, Sergey Dyasli <sergey.dyasli@...rix.com> wrote:
>>
>> This series allows to boot and run Xen PV kernels (Dom0 and DomU) with
>> CONFIG_KASAN=y. It has been used internally for some time now with good
>> results for finding memory corruption issues in Dom0 kernel.
>>
>> Only Outline instrumentation is supported at the moment.
>>
>> Patch 1 is of RFC quality
>> Patches 2-3 are independent and quite self-contained.
>
>
> Don’t you need to initialize kasan before, for example, calling kasan_alloc_pages() in patch 2?
Patch 1 is enough to correctly initialise PV Kasan. But without patch 2, lots
of false positive out-of-bounds accesses are reported once a guest starts using
PV I/O devices.
--
Thanks,
Sergey
Powered by blists - more mailing lists