Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932409AbaGNPPP (ORCPT ); Mon, 14 Jul 2014 11:15:15 -0400 Received: from qmta13.emeryville.ca.mail.comcast.net ([76.96.27.243]:49705 "EHLO qmta13.emeryville.ca.mail.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756376AbaGNPOA (ORCPT ); Mon, 14 Jul 2014 11:14:00 -0400 Date: Mon, 14 Jul 2014 10:13:56 -0500 (CDT) From: Christoph Lameter To: Andrey Ryabinin cc: "H. Peter Anvin" , Andrey Ryabinin , linux-kernel@vger.kernel.org, Dmitry Vyukov , Konstantin Serebryany , Alexey Preobrazhensky , Andrey Konovalov , Yuri Gribov , Konstantin Khlebnikov , Sasha Levin , Michal Marek , Russell King , Thomas Gleixner , Ingo Molnar , Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , linux-kbuild@vger.kernel.org, linux-arm-kernel@lists.infradead.org, x86@kernel.org, linux-mm@kvack.org Subject: Re: [RFC/PATCH -next 00/21] Address sanitizer for kernel (kasan) - dynamic memory error detector. In-Reply-To: Message-ID: References: <1404903678-8257-1-git-send-email-a.ryabinin@samsung.com> <53C08876.10209@zytor.com> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/