On Fri, Mar 6, 2015 at 8:47 AM, Luis R. Rodriguez wrote:
> If I had a technical solution to this problem I'd propose it but I don't,
> I'm just flagging it right now and hope we can come up with one.
Shortly I'll be posting part of a proactive solution I believe we
could
On Fri, Mar 06, 2015 at 11:02:50AM -0500, Konrad Rzeszutek Wilk wrote:
On Wed, Mar 04, 2015 at 05:47:03PM -0800, Luis R. Rodriguez wrote:
On Wed, Mar 4, 2015 at 6:36 AM, Andrey Ryabinin a.ryabi...@samsung.com
wrote:
On 03/03/2015 07:02 PM, Konrad Rzeszutek Wilk wrote:
If it is like
On Wed, Mar 04, 2015 at 05:47:03PM -0800, Luis R. Rodriguez wrote:
On Wed, Mar 4, 2015 at 6:36 AM, Andrey Ryabinin a.ryabi...@samsung.com
wrote:
On 03/03/2015 07:02 PM, Konrad Rzeszutek Wilk wrote:
If it is like that - then just using what had to be implemented
for the stack protection as
On 03/03/2015 07:02 PM, Konrad Rzeszutek Wilk wrote:
On Tue, Mar 03, 2015 at 06:38:20PM +0300, Andrey Ryabinin wrote:
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,
On 03/03/2015 08:20 PM, Luis R. Rodriguez wrote:
On Tue, Mar 3, 2015 at 2:06 AM, David Vrabel david.vra...@citrix.com wrote:
On 03/03/15 09:40, Luis R. Rodriguez wrote:
Andrey,
I believe that on Xen we should disable kasan, would like confirmation
Why? This is the first of heard of this.
On Wed, Mar 4, 2015 at 6:36 AM, Andrey Ryabinin a.ryabi...@samsung.com wrote:
On 03/03/2015 07:02 PM, Konrad Rzeszutek Wilk wrote:
If it is like that - then just using what had to be implemented
for the stack protection as a template ought to pave most of the
work?
Probably. I think I could
On 03/03/15 09:40, Luis R. Rodriguez wrote:
Andrey,
I believe that on Xen we should disable kasan, would like confirmation
Why? This is the first of heard of this.
from someone on xen-devel though. Here's the thing though -- if true
-- I'd like to do it *properly*, where *properly* means
On Tue, Mar 03, 2015 at 06:38:20PM +0300, Andrey Ryabinin wrote:
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,
On Tue, Mar 3, 2015 at 2:06 AM, David Vrabel david.vra...@citrix.com wrote:
On 03/03/15 09:40, Luis R. Rodriguez wrote:
Andrey,
I believe that on Xen we should disable kasan, would like confirmation
Why? This is the first of heard of this.
Andrey chimed in here confirming this.
from
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
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
On 03.03.15 at 10:40, mcg...@suse.com wrote:
Let's go down the rabbit hole for a bit. HAVE_ARCH_KASAN will be
selected on x86 when:
if X86_64 SPARSEMEM_VMEMMAP
Now Xen should not have SPARSEMEM_VMEMMAP
Why would that be?
Jan
___
12 matches
Mail list logo