From: Andrey Ryabinin <a.ryabinin@samsung.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "Luis R. Rodriguez" <mcgrof@suse.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Rusty Russell <rusty@rustcorp.com.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Chris Wright <chrisw@sous-sol.org>,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
virtualization@lists.linux-foundation.org,
Alok Kataria <akataria@vmware.com>
Subject: Re: [Xen-devel] kasan_map_early_shadow() on Xen
Date: Tue, 03 Mar 2015 18:38:20 +0300 [thread overview]
Message-ID: <54F5D56C.6020803@samsung.com> (raw)
In-Reply-To: <20150303141650.GA30332@l.oracle.com>
On 03/03/2015 05:16 PM, Konrad Rzeszutek Wilk wrote:
> On Tue, Mar 03, 2015 at 04:15:06PM +0300, Andrey Ryabinin wrote:
>> On 03/03/2015 12:40 PM, Luis R. Rodriguez wrote:
>>> Andrey,
>>>
>>> I believe that on Xen we should disable kasan, would like confirmation
>>
>> I guess Xen guests won't work with kasan because Xen guests doesn't setup shadow
>> (kasan_map_early_shadow() is not called in xen guests).
>>
>> Disabling kasan for Xen in Kconfig is undesirable because that will disable kasan
>> for allmodconfig and allyesconfig builds, but I don't see other option for now.
>
> Was there an bug reported for this? It would be good to CC the maintainers
> of Xen on that sort of thing.
>
There was no report for this. I just looked at Xen code because of this Luis's mail
and I don't see how it could work with kasan.
Fixing this might be not trivial. We need to setup shadow memory before any kasan instrumented
function will run.
This is like with -fstack-protector (you need to setup gdt before calling any stack protected function).
next prev parent reply other threads:[~2015-03-03 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 9:40 kasan_map_early_shadow() on Xen Luis R. Rodriguez
2015-03-03 10:06 ` [Xen-devel] " David Vrabel
2015-03-03 19:20 ` Luis R. Rodriguez
2015-03-04 4:53 ` Juergen Gross
2015-03-04 8:02 ` Jan Beulich
2015-03-03 10:09 ` Jan Beulich
2015-03-03 13:15 ` Andrey Ryabinin
2015-03-03 14:16 ` [Xen-devel] " Konrad Rzeszutek Wilk
2015-03-03 15:38 ` Andrey Ryabinin [this message]
2015-03-03 16:02 ` Konrad Rzeszutek Wilk
2015-03-04 14:36 ` Andrey Ryabinin
2015-03-05 1:47 ` Luis R. Rodriguez
2015-03-06 16:02 ` Konrad Rzeszutek Wilk
2015-03-06 16:47 ` Luis R. Rodriguez
2015-12-15 20:02 ` Luis R. Rodriguez
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=54F5D56C.6020803@samsung.com \
--to=a.ryabinin@samsung.com \
--cc=akataria@vmware.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@suse.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xenproject.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