From: Sergey Dyasli <sergey.dyasli@citrix.com>
To: Boris Ostrovsky <BORIS.OSTROVSKY@ORACLE.COM>
Cc: <xen-devel@lists.xen.org>, <kasan-dev@googlegroups.com>,
<linux-kernel@vger.kernel.org>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
George Dunlap <george.dunlap@citrix.com>,
Ross Lagerwall <ross.lagerwall@citrix.com>,
"sergey.dyasli@citrix.com >> Sergey Dyasli"
<sergey.dyasli@citrix.com>
Subject: Re: [RFC PATCH 0/3] basic KASAN support for Xen PV domains
Date: Fri, 20 Dec 2019 10:26:09 +0000 [thread overview]
Message-ID: <4595107c-64aa-5139-c86e-f5bff5b3d87d@citrix.com> (raw)
In-Reply-To: <7301D02C-D33F-4205-BB32-C3E61015D26E@ORACLE.COM>
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
prev parent reply other threads:[~2019-12-20 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 14:08 [RFC PATCH 0/3] basic KASAN support for Xen PV domains Sergey Dyasli
2019-12-17 14:08 ` [RFC PATCH 1/3] x86/xen: add basic KASAN support for PV kernel Sergey Dyasli
2019-12-18 9:24 ` Jürgen Groß
2019-12-19 16:42 ` Sergey Dyasli
2019-12-20 8:43 ` Jürgen Groß
2019-12-17 14:08 ` [RFC PATCH 2/3] xen: teach KASAN about grant tables Sergey Dyasli
2019-12-17 14:08 ` [RFC PATCH 3/3] xen/netback: Fix grant copy across page boundary with KASAN Sergey Dyasli
2019-12-17 15:14 ` [Xen-devel] " Durrant, Paul
2020-01-07 10:33 ` Sergey Dyasli
2019-12-17 18:06 ` [RFC PATCH 0/3] basic KASAN support for Xen PV domains Boris Ostrovsky
2019-12-20 10:26 ` Sergey Dyasli [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=4595107c-64aa-5139-c86e-f5bff5b3d87d@citrix.com \
--to=sergey.dyasli@citrix.com \
--cc=BORIS.OSTROVSKY@ORACLE.COM \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=george.dunlap@citrix.com \
--cc=glider@google.com \
--cc=jgross@suse.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.org \
/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).