From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrey Ryabinin <a.ryabinin@samsung.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"Luis R. Rodriguez" <mcgrof@suse.com>,
"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, 3 Mar 2015 09:16:50 -0500 [thread overview]
Message-ID: <20150303141650.GA30332@l.oracle.com> (raw)
In-Reply-To: <54F5B3DA.70203@samsung.com>
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.
Thanks!
.. snip..
> > [0] https://lkml.org/lkml/2015/2/23/328
If you look at the other x86 pulls - you will see that the authors
also missed enabling it on 32-bit kernels!
> >
> > Luis
> >
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrey Ryabinin <a.ryabinin@samsung.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, 3 Mar 2015 09:16:50 -0500 [thread overview]
Message-ID: <20150303141650.GA30332@l.oracle.com> (raw)
In-Reply-To: <54F5B3DA.70203@samsung.com>
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.
Thanks!
.. snip..
> > [0] https://lkml.org/lkml/2015/2/23/328
If you look at the other x86 pulls - you will see that the authors
also missed enabling it on 32-bit kernels!
> >
> > Luis
> >
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-03-03 14:16 UTC|newest]
Thread overview: 43+ 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-03 19:20 ` Luis R. Rodriguez
2015-03-04 4:53 ` Juergen Gross
2015-03-04 4:53 ` Juergen Gross
2015-03-04 8:02 ` Jan Beulich
2015-03-04 8:02 ` [Xen-devel] " Jan Beulich
2015-03-04 8:02 ` Jan Beulich
2015-03-04 4:53 ` Juergen Gross
2015-03-03 19:20 ` Luis R. Rodriguez
2015-03-03 10:06 ` David Vrabel
2015-03-03 10:06 ` [Xen-devel] " David Vrabel
2015-03-03 10:09 ` Jan Beulich
2015-03-03 10:09 ` Jan Beulich
2015-03-03 10:09 ` Jan Beulich
2015-03-03 13:15 ` Andrey Ryabinin
2015-03-03 13:15 ` Andrey Ryabinin
2015-03-03 13:15 ` Andrey Ryabinin
2015-03-03 14:16 ` Konrad Rzeszutek Wilk
2015-03-03 14:16 ` Konrad Rzeszutek Wilk [this message]
2015-03-03 14:16 ` [Xen-devel] " Konrad Rzeszutek Wilk
2015-03-03 15:38 ` Andrey Ryabinin
2015-03-03 15:38 ` Andrey Ryabinin
2015-03-03 15:38 ` [Xen-devel] " Andrey Ryabinin
2015-03-03 16:02 ` Konrad Rzeszutek Wilk
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:02 ` [Xen-devel] " Konrad Rzeszutek Wilk
2015-03-06 16:02 ` Konrad Rzeszutek Wilk
2015-03-06 16:47 ` Luis R. Rodriguez
2015-03-06 16:47 ` Luis R. Rodriguez
2015-03-06 16:47 ` [Xen-devel] " Luis R. Rodriguez
2015-12-15 20:02 ` Luis R. Rodriguez
2015-12-15 20:02 ` Luis R. Rodriguez
2015-12-15 20:02 ` Luis R. Rodriguez
2015-03-05 1:47 ` Luis R. Rodriguez
2015-03-05 1:47 ` [Xen-devel] " Luis R. Rodriguez
2015-03-04 14:36 ` Andrey Ryabinin
2015-03-04 14:36 ` Andrey Ryabinin
2015-03-03 16:02 ` Konrad Rzeszutek Wilk
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=20150303141650.GA30332@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=a.ryabinin@samsung.com \
--cc=akataria@vmware.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.