Message ID | 20191217140804.27364-1-sergey.dyasli@citrix.com (mailing list archive) |
---|---|
Headers | show |
Series | basic KASAN support for Xen PV domains | expand |
> On Dec 17, 2019, at 9:08 AM, Sergey Dyasli <sergey.dyasli@citrix.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? -boris
On 17/12/2019 18:06, Boris Ostrovsky wrote: > > >> On Dec 17, 2019, at 9:08 AM, Sergey Dyasli <sergey.dyasli@citrix.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