From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B51CDC433F5 for ; Fri, 11 Mar 2022 10:49:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Date:Subject:CC:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=PDMch8zuhSmJq3onePGiHfaTHKMTnUr2G1R4+8LLli8=; b=3KX/0//8jIFpE6 7dG6Dl4cppKXOyvaNYkRbGaHUNUUaLeZRIZLQq2EH0umtnQqp24x3JjwLWz1VTUnEVc9aAgntiLAx 1uUu0HrwmLoyv+Fg1D+yO5b3CmVAtwBGRveqK3XzWR+SQqwoVRvcultjx86JleP23PqlvIb3mW9IP Y59mNUkpCxBcAfQ5ns59sFNzszJAYcYbOqjjxpJjPLCotJIRSwUs9hOsVkCI6yu6FRrNMBwM3x43R gM6pK3iwZpsOtIDakpWAS+jaxzy5VPp2WGTa5cjA4fk7A4q8V2WxVlpIJeEZkv4qnXcpu/aYot/4Z RxIFpqS3dg4PamTl3xxw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nScoi-00G6bv-Ct; Fri, 11 Mar 2022 10:48:16 +0000 Received: from mailgw01.mediatek.com ([216.200.240.184]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nScoa-00G6aH-Sw for linux-arm-kernel@lists.infradead.org; Fri, 11 Mar 2022 10:48:12 +0000 X-UUID: b4065bdd41a047a0a085082dd6fd0bcc-20220311 X-UUID: b4065bdd41a047a0a085082dd6fd0bcc-20220311 Received: from mtkcas66.mediatek.inc [(172.29.193.44)] by mailgw01.mediatek.com (envelope-from ) (musrelay.mediatek.com ESMTP with TLSv1.2 ECDHE-RSA-AES256-SHA384 256/256) with ESMTP id 100717420; Fri, 11 Mar 2022 03:48:01 -0700 Received: from mtkexhb01.mediatek.inc (172.21.101.102) by MTKMBS62N2.mediatek.inc (172.29.193.42) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 11 Mar 2022 02:47:59 -0800 Received: from mtkcas11.mediatek.inc (172.21.101.40) by mtkexhb01.mediatek.inc (172.21.101.102) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 11 Mar 2022 18:47:52 +0800 Received: from mtksdccf07.mediatek.inc (172.21.84.99) by mtkcas11.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Fri, 11 Mar 2022 18:47:52 +0800 From: Lecopzer Chen To: CC: , , , , , , , , , , , , , , , , , Subject: Re: [PATCH v3 1/2] arm: kasan: support CONFIG_KASAN_VMALLOC Date: Fri, 11 Mar 2022 18:47:52 +0800 Message-ID: <20220311104752.2616-1-lecopzer.chen@mediatek.com> X-Mailer: git-send-email 2.18.0 In-Reply-To: References: MIME-Version: 1.0 X-MTK: N X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220311_024808_984007_96160B9F X-CRM114-Status: GOOD ( 23.36 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org > On Sun, Feb 27, 2022 at 09:47:25PM +0800, Lecopzer Chen wrote: > > Simply make shadow of vmalloc area mapped on demand. > > > > Since the virtual address of vmalloc for Arm is also between > > MODULE_VADDR and 0x100000000 (ZONE_HIGHMEM), which means the shadow > > address has already included between KASAN_SHADOW_START and > > KASAN_SHADOW_END. > > Thus we need to change nothing for memory map of Arm. > > > > This can fix ARM_MODULE_PLTS with KASan, support KASan for higmem > > and provide the first step to support CONFIG_VMAP_STACK with Arm. > > > > Signed-off-by: Lecopzer Chen > > --- > > arch/arm/Kconfig | 1 + > > arch/arm/include/asm/kasan_def.h | 11 ++++++++++- > > arch/arm/mm/kasan_init.c | 6 +++++- > > 3 files changed, 16 insertions(+), 2 deletions(-) > > > > diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig > > index 4c97cb40eebb..78250e246cc6 100644 > > --- a/arch/arm/Kconfig > > +++ b/arch/arm/Kconfig > > @@ -72,6 +72,7 @@ config ARM > > select HAVE_ARCH_KFENCE if MMU && !XIP_KERNEL > > select HAVE_ARCH_KGDB if !CPU_ENDIAN_BE32 && MMU > > select HAVE_ARCH_KASAN if MMU && !XIP_KERNEL > > + select HAVE_ARCH_KASAN_VMALLOC if HAVE_ARCH_KASAN > > select HAVE_ARCH_MMAP_RND_BITS if MMU > > select HAVE_ARCH_PFN_VALID > > select HAVE_ARCH_SECCOMP > > diff --git a/arch/arm/include/asm/kasan_def.h b/arch/arm/include/asm/kasan_def.h > > index 5739605aa7cf..96fd1d3b5a0c 100644 > > --- a/arch/arm/include/asm/kasan_def.h > > +++ b/arch/arm/include/asm/kasan_def.h > > @@ -19,7 +19,16 @@ > > * space to use as shadow memory for KASan as follows: > > * > > * +----+ 0xffffffff > > - * | | \ > > + * | |\ > > + * | | |-> ZONE_HIGHMEM for vmalloc virtual address space. > > + * | | | Such as vmalloc(), GFP_HIGHUSER (__GFP__HIGHMEM), > > + * | | | module address using ARM_MODULE_PLTS, etc. > > + * | | | > > + * | | | If CONFIG_KASAN_VMALLOC=y, this area would populate > > + * | | | shadow address on demand. > > + * | |/ > > This diagram is incorrect. We already have the memory layout in > Documentation/arm/memory.rst, so we don't need another set of > documentation that is misleading. Ok, should I send a v4 to remove this? BRs, Lecopzer _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel