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 X-Spam-Level: X-Spam-Status: No, score=-13.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_ADSP_CUSTOM_MED,DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8A006C433E1 for ; Fri, 14 Aug 2020 18:31:53 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4EAE420774 for ; Fri, 14 Aug 2020 18:31:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="kjvxZD9u"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=google.com header.i=@google.com header.b="iN00ACnX" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4EAE420774 Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:To:From:Subject:References:Mime-Version:Message-Id: In-Reply-To:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=HxJU5G5yHP8WsJr10uUTe+AxO2D1qQfHYGsJvU4w3zw=; b=kjvxZD9uS7haALXPpkUrWnYK6 6ZJbt5/8k+PBUIa9XG/6Xhfj/uYIWxqr8+/i+av/y1zR2oWcHf4co5qiGRMrAVl0plK1ku5JT9msF S0pMfDshtP0EUpBPPFzjEkn1nN0hSwnKScloKQoN2XpN/lKJmtGOrl3m7al0CXCFLpilHOKPYTTfJ 8Vm1t1rrRdPk6lEhJ7OTw1sLBQXYWvF8vhKd2ZNGg3PavZqDi5hsdzCNiaoYGY6+iYm6od1aW2cpU SGsqVIx+A+/FQS95OeUhFk5EJh5U2kCg+pT0Rd2/2TdsQ6wAV3RuW8wy+pDRzCmM7EGpcW9Un3+4/ 6DNaTVUiA==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1k6daE-0006ch-6E; Fri, 14 Aug 2020 17:33:38 +0000 Received: from mail-wr1-x449.google.com ([2a00:1450:4864:20::449]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1k6dVD-0003eH-72 for linux-arm-kernel@lists.infradead.org; Fri, 14 Aug 2020 17:28:40 +0000 Received: by mail-wr1-x449.google.com with SMTP id f7so3593266wrs.8 for ; Fri, 14 Aug 2020 10:28:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:in-reply-to:message-id:mime-version:references:subject:from:to :cc; bh=G1m+mBc5DHN9N1yWiSk6nb4X2zq+d5nDMgJyTLNPPRc=; b=iN00ACnXSigVftuw0EX8zS6BlCZnflPn/Q/U+4zt3OGmV18sNHa8QInILgUE3bS1S3 +uaZ0yTubCRhMfO57RaPHcuTDWncpDx0+fuTlmzvwx/KHz0kyKif5pbWIpihjJ7pDOyI FkHIfnJt0HsbPI80RU8DfmVLmHCInLIlVsNUFfjboDUt80RBuDkFyDZt2ZqnFr7TOSWK VaVuQLtjwRVXX69n6Y9ra/d6a1d8BAdl8bpvGHA14kF8zqvCgMUPZr68ys/Y3JBy/FAA kk3ZPayQN2mg/AatquaXwle9h+/8OfNC1Bo52nN96Tf9POfPQHBPOCHfs9K+l84SbCvP E6Lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:in-reply-to:message-id:mime-version :references:subject:from:to:cc; bh=G1m+mBc5DHN9N1yWiSk6nb4X2zq+d5nDMgJyTLNPPRc=; b=QsnU/LKVTjfDwCX3IhreQnA7zyh6kvBkX71DRMJ7Hk+ZX8qIpbIqpvTnKYbCPfKIOg fmahouaofmiQkeiao+7P/uqh75LBcdYGQAyj/fRxQRCXYw/prs9CSSkIiovsqdh6b/nb iUiASUYH1kLPTNnpvcVEAyZWwL2/kYVxlDoh5oPlTsEiR+0v8QjSpJmFDh4ZqQ3b1hb8 xZSJi4IYaxhVAtQxS9gBxlzqzTQ/dAYVsATN+GfRQV5G61RwhiSbJ/MEc7xCoaZVPfpv LuasV4RLI/uCJg/fkyWoJiYzxysXcvXgg0gap432FTPEeS2w+JEBeGN4DIG/zGd0RHDv ArTw== X-Gm-Message-State: AOAM532rmq/iplWsPKNWyj46bJLN6+6+vhf7+o9bmBDZhXZQ9/BgqF8C 2lDbPY0+774CIxxuYfgWGvSIYhTRsbbYjpUB X-Google-Smtp-Source: ABdhPJwmPyfcBdf/Nisj5qqVZNt2nZ+O/Vnc7pjOKCV5aU3t/ELZ7Z9s59RcLiYOKvcmEwq9jb4R/mo0VgSbpBiG X-Received: by 2002:a1c:32c3:: with SMTP id y186mr3400306wmy.15.1597426103272; Fri, 14 Aug 2020 10:28:23 -0700 (PDT) Date: Fri, 14 Aug 2020 19:27:07 +0200 In-Reply-To: Message-Id: <8a499341bbe4767a4ee1d3b8acb8bd83420ce3a5.1597425745.git.andreyknvl@google.com> Mime-Version: 1.0 References: X-Mailer: git-send-email 2.28.0.220.ged08abb693-goog Subject: [PATCH 25/35] kasan: introduce CONFIG_KASAN_HW_TAGS From: Andrey Konovalov To: Dmitry Vyukov , Vincenzo Frascino , Catalin Marinas , kasan-dev@googlegroups.com X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200814_132827_355968_4B8FCB73 X-CRM114-Status: GOOD ( 15.56 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Marco Elver , Elena Petrova , Andrey Konovalov , Kevin Brodsky , Will Deacon , Branislav Rankov , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Alexander Potapenko , linux-arm-kernel@lists.infradead.org, Andrey Ryabinin , Andrew Morton , Evgenii Stepanov 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 This patch adds a configuration option for a new KASAN mode called hardware tag-based KASAN. This mode uses the memory tagging approach like the software tag-based mode, but relies on arm64 Memory Tagging Extension feature for tag management and access checking. Signed-off-by: Andrey Konovalov --- lib/Kconfig.kasan | 46 ++++++++++++++++++++++++++++++++-------------- 1 file changed, 32 insertions(+), 14 deletions(-) diff --git a/lib/Kconfig.kasan b/lib/Kconfig.kasan index e500c18cbe79..0d4160ce5ee8 100644 --- a/lib/Kconfig.kasan +++ b/lib/Kconfig.kasan @@ -6,7 +6,10 @@ config HAVE_ARCH_KASAN config HAVE_ARCH_KASAN_SW_TAGS bool -config HAVE_ARCH_KASAN_VMALLOC +config HAVE_ARCH_KASAN_HW_TAGS + bool + +config HAVE_ARCH_KASAN_VMALLOC bool config CC_HAS_KASAN_GENERIC @@ -20,10 +23,11 @@ config CC_HAS_WORKING_NOSANITIZE_ADDRESS menuconfig KASAN bool "KASAN: runtime memory debugger" - depends on (HAVE_ARCH_KASAN && CC_HAS_KASAN_GENERIC) || \ - (HAVE_ARCH_KASAN_SW_TAGS && CC_HAS_KASAN_SW_TAGS) + depends on (((HAVE_ARCH_KASAN && CC_HAS_KASAN_GENERIC) || \ + (HAVE_ARCH_KASAN_SW_TAGS && CC_HAS_KASAN_SW_TAGS)) && \ + CC_HAS_WORKING_NOSANITIZE_ADDRESS) || \ + HAVE_ARCH_KASAN_HW_TAGS depends on (SLUB && SYSFS) || (SLAB && !DEBUG_SLAB) - depends on CC_HAS_WORKING_NOSANITIZE_ADDRESS select SLUB_DEBUG if SLUB select CONSTRUCTORS select STACKDEPOT @@ -38,13 +42,18 @@ choice prompt "KASAN mode" default KASAN_GENERIC help - KASAN has two modes: generic KASAN (similar to userspace ASan, - x86_64/arm64/xtensa, enabled with CONFIG_KASAN_GENERIC) and - software tag-based KASAN (a version based on software memory - tagging, arm64 only, similar to userspace HWASan, enabled with - CONFIG_KASAN_SW_TAGS). + KASAN has three modes: + 1. generic KASAN (similar to userspace ASan, + x86_64/arm64/xtensa, enabled with CONFIG_KASAN_GENERIC), + 2. software tag-based KASAN (arm64 only, based on software + memory tagging (similar to userspace HWASan), enabled with + CONFIG_KASAN_SW_TAGS), and + 3. hardware tag-based KASAN (arm64-only, based hardware + memory tagging (MTE), enabled with CONFIG_KASAN_HW_TAGS). + + All KASAN modes are strictly debugging features. - Both generic and tag-based KASAN are strictly debugging features. + For better error detection enable CONFIG_STACKTRACE. config KASAN_GENERIC bool "Generic mode" @@ -61,8 +70,6 @@ config KASAN_GENERIC and introduces an overhead of ~x1.5 for the rest of the allocations. The performance slowdown is ~x3. - For better error detection enable CONFIG_STACKTRACE. - Currently CONFIG_KASAN_GENERIC doesn't work with CONFIG_DEBUG_SLAB (the resulting kernel does not boot). @@ -83,15 +90,25 @@ config KASAN_SW_TAGS casting and comparison, as it embeds tags into the top byte of each pointer. - For better error detection enable CONFIG_STACKTRACE. - Currently CONFIG_KASAN_SW_TAGS doesn't work with CONFIG_DEBUG_SLAB (the resulting kernel does not boot). +config KASAN_HW_TAGS + bool "Hardware tag-based mode" + depends on HAVE_ARCH_KASAN_HW_TAGS + depends on SLUB + help + Enables hardware tag-based KASAN mode. + + This mode requires both Memory Tagging Extension and Top Byte Ignore + support by the CPU and therefore is only supported for modern arm64 + CPUs (MTE added in ARMv8.5 ISA). + endchoice choice prompt "Instrumentation type" + depends on KASAN_GENERIC || KASAN_SW_TAGS default KASAN_OUTLINE config KASAN_OUTLINE @@ -115,6 +132,7 @@ endchoice config KASAN_STACK_ENABLE bool "Enable stack instrumentation (unsafe)" if CC_IS_CLANG && !COMPILE_TEST + depends on KASAN_GENERIC || KASAN_SW_TAGS help The LLVM stack address sanitizer has a know problem that causes excessive stack usage in a lot of functions, see -- 2.28.0.220.ged08abb693-goog _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel