[01/35] kasan: KASAN_VMALLOC depends on KASAN_GENERIC

Message ID	c36842a403be0fbf3dd63b16a7cd231ebd6d4d5b.1597425745.git.andreyknvl@google.com (mailing list archive)
State	New, archived
Headers	show Return-Path: <SRS0=uP9R=BY=lists.infradead.org=linux-arm-kernel-bounces+patchwork-linux-arm=patchwork.kernel.org@kernel.org> DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D901A2078D Date: Fri, 14 Aug 2020 19:26:43 +0200 In-Reply-To: <cover.1597425745.git.andreyknvl@google.com> Message-Id: <c36842a403be0fbf3dd63b16a7cd231ebd6d4d5b.1597425745.git.andreyknvl@google.com> Mime-Version: 1.0 References: <cover.1597425745.git.andreyknvl@google.com> Subject: [PATCH 01/35] kasan: KASAN_VMALLOC depends on KASAN_GENERIC From: Andrey Konovalov <andreyknvl@google.com> To: Dmitry Vyukov <dvyukov@google.com>, Vincenzo Frascino <vincenzo.frascino@arm.com>, Catalin Marinas <catalin.marinas@arm.com>, kasan-dev@googlegroups.com summary: Content analysis details: (-7.7 points) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no trust [2a00:1450:4864:20:0:0:0:34a listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record -7.5 USER_IN_DEF_DKIM_WL From: address is in the default DKIM white-list 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -0.0 DKIMWL_WL_MED DKIMwl.org - Medium sender Precedence: list Cc: Marco Elver <elver@google.com>, Elena Petrova <lenaptr@google.com>, Andrey Konovalov <andreyknvl@google.com>, Kevin Brodsky <kevin.brodsky@arm.com>, Will Deacon <will.deacon@arm.com>, Branislav Rankov <Branislav.Rankov@arm.com>, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Alexander Potapenko <glider@google.com>, linux-arm-kernel@lists.infradead.org, Andrey Ryabinin <aryabinin@virtuozzo.com>, Andrew Morton <akpm@linux-foundation.org>, Evgenii Stepanov <eugenis@google.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" <linux-arm-kernel-bounces@lists.infradead.org> Errors-To: linux-arm-kernel-bounces+patchwork-linux-arm=patchwork.kernel.org@lists.infradead.org
Series	kasan: add hardware tag-based mode for arm64 \| expand [00/35] kasan: add hardware tag-based mode for arm64 [01/35] kasan: KASAN_VMALLOC depends on KASAN_GENERIC [02/35] kasan: group vmalloc code [03/35] kasan: shadow declarations only for software modes [04/35] kasan: rename (un)poison_shadow to (un)poison_memory [05/35] kasan: rename KASAN_SHADOW_* to KASAN_GRANULE_* [06/35] kasan: only build init.c for software modes [07/35] kasan: split out shadow.c from common.c [08/35] kasan: rename generic/tags_report.c files [09/35] kasan: don't duplicate config dependencies [10/35] kasan: hide invalid free check implementation [11/35] kasan: decode stack frame only with KASAN_STACK_ENABLE [12/35] kasan, arm64: only init shadow for software modes [13/35] kasan, arm64: only use kasan_depth for software modes [14/35] kasan: rename addr_has_shadow to addr_has_metadata [15/35] kasan: rename print_shadow_for_address to print_memory_metadata [16/35] kasan: kasan_non_canonical_hook only for software modes [17/35] kasan: rename SHADOW layout macros to META [18/35] kasan: separate metadata_fetch_row for each mode [19/35] kasan: don't allow SW_TAGS with ARM64_MTE [20/35] arm64: mte: Add in-kernel MTE helpers [21/35] arm64: mte: Add in-kernel tag fault handler [22/35] arm64: mte: Enable in-kernel MTE [23/35] arm64: mte: Convert gcr_user into an exclude mask [24/35] arm64: mte: Switch GCR_EL1 in kernel entry and exit [25/35] kasan: introduce CONFIG_KASAN_HW_TAGS [26/35] kasan, arm64: Enable TBI EL1 [27/35] kasan, arm64: align allocations for HW_TAGS [28/35] kasan: define KASAN_GRANULE_SIZE for HW_TAGS [29/35] kasan, x86, s390: update undef CONFIG_KASAN [30/35] kasan, arm64: expand CONFIG_KASAN checks [31/35] kasan, arm64: implement HW_TAGS runtime [32/35] kasan, arm64: print report from tag fault handler [33/35] kasan, slub: reset tags when accessing metadata [34/35] kasan, arm64: enable CONFIG_KASAN_HW_TAGS [35/35] kasan: add documentation for hardware tag-based mode

Message ID

c36842a403be0fbf3dd63b16a7cd231ebd6d4d5b.1597425745.git.andreyknvl@google.com (mailing list archive)

State

New, archived

Headers

DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D901A2078D
Date: Fri, 14 Aug 2020 19:26:43 +0200
In-Reply-To: <cover.1597425745.git.andreyknvl@google.com>
Message-Id: 
 <c36842a403be0fbf3dd63b16a7cd231ebd6d4d5b.1597425745.git.andreyknvl@google.com>
Mime-Version: 1.0
References: <cover.1597425745.git.andreyknvl@google.com>
Subject: [PATCH 01/35] kasan: KASAN_VMALLOC depends on KASAN_GENERIC
From: Andrey Konovalov <andreyknvl@google.com>
To: Dmitry Vyukov <dvyukov@google.com>,
 Vincenzo Frascino <vincenzo.frascino@arm.com>,
 Catalin Marinas <catalin.marinas@arm.com>, kasan-dev@googlegroups.com
Precedence: list
Cc: Marco Elver <elver@google.com>, Elena Petrova <lenaptr@google.com>,
 Andrey Konovalov <andreyknvl@google.com>,
 Kevin Brodsky <kevin.brodsky@arm.com>, Will Deacon <will.deacon@arm.com>,
 Branislav Rankov <Branislav.Rankov@arm.com>, linux-kernel@vger.kernel.org,
 linux-mm@kvack.org, Alexander Potapenko <glider@google.com>,
 linux-arm-kernel@lists.infradead.org,
 Andrey Ryabinin <aryabinin@virtuozzo.com>,
 Andrew Morton <akpm@linux-foundation.org>,
 Evgenii Stepanov <eugenis@google.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "linux-arm-kernel" <linux-arm-kernel-bounces@lists.infradead.org>
Errors-To: 
 linux-arm-kernel-bounces+patchwork-linux-arm=patchwork.kernel.org@lists.infradead.org

Series

kasan: add hardware tag-based mode for arm64 | expand

Commit Message

Andrey Konovalov Aug. 14, 2020, 5:26 p.m. UTC

Currently only generic KASAN mode supports vmalloc, reflect that
in the config.

Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
---
 lib/Kconfig.kasan | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/Kconfig.kasan b/lib/Kconfig.kasan
index 047b53dbfd58..e1d55331b618 100644
--- a/lib/Kconfig.kasan
+++ b/lib/Kconfig.kasan
@@ -156,7 +156,7 @@  config KASAN_SW_TAGS_IDENTIFY
 
 config KASAN_VMALLOC
 	bool "Back mappings in vmalloc space with real shadow memory"
-	depends on HAVE_ARCH_KASAN_VMALLOC
+	depends on KASAN_GENERIC && HAVE_ARCH_KASAN_VMALLOC
 	help
 	  By default, the shadow region for vmalloc space is the read-only
 	  zero page. This means that KASAN cannot detect errors involving

[01/35] kasan: KASAN_VMALLOC depends on KASAN_GENERIC

Commit Message

Patch