lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <alpine.DEB.2.11.1407141012520.25405@gentwo.org> Date: Mon, 14 Jul 2014 10:13:56 -0500 (CDT) From: Christoph Lameter <cl@...two.org> To: Andrey Ryabinin <ryabinin.a.a@...il.com> cc: "H. Peter Anvin" <hpa@...or.com>, Andrey Ryabinin <a.ryabinin@...sung.com>, linux-kernel@...r.kernel.org, Dmitry Vyukov <dvyukov@...gle.com>, Konstantin Serebryany <kcc@...gle.com>, Alexey Preobrazhensky <preobr@...gle.com>, Andrey Konovalov <adech.fo@...il.com>, Yuri Gribov <tetra2005@...il.com>, Konstantin Khlebnikov <koct9i@...il.com>, Sasha Levin <sasha.levin@...cle.com>, Michal Marek <mmarek@...e.cz>, Russell King <linux@....linux.org.uk>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Pekka Enberg <penberg@...nel.org>, David Rientjes <rientjes@...gle.com>, Joonsoo Kim <iamjoonsoo.kim@....com>, Andrew Morton <akpm@...ux-foundation.org>, linux-kbuild@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, x86@...nel.org, linux-mm@...ck.org Subject: Re: [RFC/PATCH -next 00/21] Address sanitizer for kernel (kasan) - dynamic memory error detector. On Sun, 13 Jul 2014, Andrey Ryabinin wrote: > > How does that work when memory is sparsely populated? > > > > Sparsemem configurations currently may not work with kasan. > I suppose I will have to move shadow area to vmalloc address space and > make it (shadow) sparse too if needed. Well it seems to work with sparsemem / vmemmap? So non vmmemmapped configs of sparsemem only. vmemmmap can also handle holes in memory. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists