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=-18.9 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1,USER_IN_DEF_DKIM_WL 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 11C2BC47423 for ; Thu, 1 Oct 2020 18:04:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A82902145D for ; Thu, 1 Oct 2020 18:04:07 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="dPA+Od53" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733019AbgJASEG (ORCPT ); Thu, 1 Oct 2020 14:04:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34640 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730029AbgJASEG (ORCPT ); Thu, 1 Oct 2020 14:04:06 -0400 Received: from mail-wr1-x441.google.com (mail-wr1-x441.google.com [IPv6:2a00:1450:4864:20::441]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 72122C0613D0 for ; Thu, 1 Oct 2020 11:04:05 -0700 (PDT) Received: by mail-wr1-x441.google.com with SMTP id e16so6873735wrm.2 for ; Thu, 01 Oct 2020 11:04:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=0OdyXaVNiyIQMSnkmN1U5DBWCyVDZmuQfjlNhLtDrKs=; b=dPA+Od53q5f/HBtQwvz6tXehIq+teMdNnK314CY3s0ajOt31vt/u/6D54Q/Ix/LC86 VtbYmG/LRaO//ScEveC5LTytEFM1+3pyoHPWuviFMpXhjPErq3Ufy2aSE62Z1E54Jr6x fqWFaqqQi3HGXr9rIfyLZrmvxYUAsZ3HsNF8y8akiDP5oppHmkSq2PJk0baeSBr0X0ou AUH/o1uBlIATCN1Px1ykRaBmK5Mn1QE0VhyzivGl4dPLnU2lDdrakcyrmDF6NyYXkxzN SJIsUNhdD1tp2kvB482PCt/cq9B2r/JGgCl6SNVrMLV76ZijAIXnbqO8oNjGq3WyT6CK Rs/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=0OdyXaVNiyIQMSnkmN1U5DBWCyVDZmuQfjlNhLtDrKs=; b=K++IQ0M12z5zpGW6Khy4IhHWPRSLE8i5UpIJvNBjgxgEPV8LvZQGqcNWEzqhxr3lUR J/eitAHk8jhSuN4pfvmrmsZLzKfJvG4n0keXq+sqOaFuhtoMnnk4+qOTn0gZmGMHa5oO Rn+/Ww0ZmbJ8EIA8v22wR/ErfRCz9mayZLGk7ph8oPJbM2iDQtooFKE+usT+iU1HQXwT 1PVr2+62ifi9fxTVsqQJmb8KP0cja6BjjWHexge8pMv8UJJ9S/Os1Ayz6D9+9fxmum5n Bdg363uOO/BljlK/1ioN/lV5lRrgr8wHh1sAelZTtEgEaauuI6/qgHcMru4M3KdkFITe 888Q== X-Gm-Message-State: AOAM530+dmNAtt/+KcyekaTrrK+L4l8Vl8cm9zSdGoUefWkAQDIhgWNM DiO4P9j55j6V+u7zhdxsWCBUww== X-Google-Smtp-Source: ABdhPJwzl9G8I0FIwZnl+qK3rpBAlZVN5JVj57b7Bi+4u6kcK9IXkcXgdVGaQG1V73bZU6YmgI5YXQ== X-Received: by 2002:adf:e4cf:: with SMTP id v15mr10259531wrm.174.1601575443811; Thu, 01 Oct 2020 11:04:03 -0700 (PDT) Received: from elver.google.com ([100.105.32.75]) by smtp.gmail.com with ESMTPSA id k6sm950946wmf.30.2020.10.01.11.04.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 01 Oct 2020 11:04:03 -0700 (PDT) Date: Thu, 1 Oct 2020 20:03:57 +0200 From: elver@google.com To: Andrey Konovalov Cc: Dmitry Vyukov , Vincenzo Frascino , Catalin Marinas , kasan-dev@googlegroups.com, Andrey Ryabinin , Alexander Potapenko , Evgenii Stepanov , Elena Petrova , Branislav Rankov , Kevin Brodsky , Will Deacon , Andrew Morton , linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 39/39] kasan: add documentation for hardware tag-based mode Message-ID: <20201001180357.GW4162920@elver.google.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.14.5 (2020-06-23) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 25, 2020 at 12:50AM +0200, Andrey Konovalov wrote: > Add documentation for hardware tag-based KASAN mode and also add some > clarifications for software tag-based mode. > > Signed-off-by: Andrey Konovalov > Signed-off-by: Vincenzo Frascino Reviewed-by: Marco Elver > --- > Change-Id: Ib46cb444cfdee44054628940a82f5139e10d0258 > --- > Documentation/dev-tools/kasan.rst | 78 ++++++++++++++++++++++--------- > 1 file changed, 57 insertions(+), 21 deletions(-) > > diff --git a/Documentation/dev-tools/kasan.rst b/Documentation/dev-tools/kasan.rst > index a3030fc6afe5..d2d47c82a7b9 100644 > --- a/Documentation/dev-tools/kasan.rst > +++ b/Documentation/dev-tools/kasan.rst > @@ -5,12 +5,14 @@ Overview > -------- > > KernelAddressSANitizer (KASAN) is a dynamic memory error detector designed to > -find out-of-bound and use-after-free bugs. KASAN has two modes: generic KASAN > -(similar to userspace ASan) and software tag-based KASAN (similar to userspace > -HWASan). > +find out-of-bound and use-after-free bugs. KASAN has three modes: > +1. generic KASAN (similar to userspace ASan), > +2. software tag-based KASAN (similar to userspace HWASan), > +3. hardware tag-based KASAN (based on hardware memory tagging). > > -KASAN uses compile-time instrumentation to insert validity checks before every > -memory access, and therefore requires a compiler version that supports that. > +Software KASAN modes (1 and 2) use compile-time instrumentation to insert > +validity checks before every memory access, and therefore require a compiler > +version that supports that. > > Generic KASAN is supported in both GCC and Clang. With GCC it requires version > 8.3.0 or later. With Clang it requires version 7.0.0 or later, but detection of > @@ -19,7 +21,7 @@ out-of-bounds accesses for global variables is only supported since Clang 11. > Tag-based KASAN is only supported in Clang and requires version 7.0.0 or later. > > Currently generic KASAN is supported for the x86_64, arm64, xtensa, s390 and > -riscv architectures, and tag-based KASAN is supported only for arm64. > +riscv architectures, and tag-based KASAN modes are supported only for arm64. > > Usage > ----- > @@ -28,14 +30,16 @@ To enable KASAN configure kernel with:: > > CONFIG_KASAN = y > > -and choose between CONFIG_KASAN_GENERIC (to enable generic KASAN) and > -CONFIG_KASAN_SW_TAGS (to enable software tag-based KASAN). > +and choose between CONFIG_KASAN_GENERIC (to enable generic KASAN), > +CONFIG_KASAN_SW_TAGS (to enable software tag-based KASAN), and > +CONFIG_KASAN_HW_TAGS (to enable hardware tag-based KASAN). > > -You also need to choose between CONFIG_KASAN_OUTLINE and CONFIG_KASAN_INLINE. > -Outline and inline are compiler instrumentation types. The former produces > -smaller binary while the latter is 1.1 - 2 times faster. > +For software modes, you also need to choose between CONFIG_KASAN_OUTLINE and > +CONFIG_KASAN_INLINE. Outline and inline are compiler instrumentation types. > +The former produces smaller binary while the latter is 1.1 - 2 times faster. > > -Both KASAN modes work with both SLUB and SLAB memory allocators. > +Both software KASAN modes work with both SLUB and SLAB memory allocators, > +hardware tag-based KASAN currently only support SLUB. > For better bug detection and nicer reporting, enable CONFIG_STACKTRACE. > > To augment reports with last allocation and freeing stack of the physical page, > @@ -196,17 +200,24 @@ and the second to last. > Software tag-based KASAN > ~~~~~~~~~~~~~~~~~~~~~~~~ > > -Tag-based KASAN uses the Top Byte Ignore (TBI) feature of modern arm64 CPUs to > -store a pointer tag in the top byte of kernel pointers. Like generic KASAN it > -uses shadow memory to store memory tags associated with each 16-byte memory > +Software tag-based KASAN requires software memory tagging support in the form > +of HWASan-like compiler instrumentation (see HWASan documentation for details). > + > +Software tag-based KASAN is currently only implemented for arm64 architecture. > + > +Software tag-based KASAN uses the Top Byte Ignore (TBI) feature of arm64 CPUs > +to store a pointer tag in the top byte of kernel pointers. Like generic KASAN > +it uses shadow memory to store memory tags associated with each 16-byte memory > cell (therefore it dedicates 1/16th of the kernel memory for shadow memory). > > -On each memory allocation tag-based KASAN generates a random tag, tags the > -allocated memory with this tag, and embeds this tag into the returned pointer. > +On each memory allocation software tag-based KASAN generates a random tag, tags > +the allocated memory with this tag, and embeds this tag into the returned > +pointer. > + > Software tag-based KASAN uses compile-time instrumentation to insert checks > before each memory access. These checks make sure that tag of the memory that > is being accessed is equal to tag of the pointer that is used to access this > -memory. In case of a tag mismatch tag-based KASAN prints a bug report. > +memory. In case of a tag mismatch software tag-based KASAN prints a bug report. > > Software tag-based KASAN also has two instrumentation modes (outline, that > emits callbacks to check memory accesses; and inline, that performs the shadow > @@ -215,9 +226,34 @@ simply printed from the function that performs the access check. With inline > instrumentation a brk instruction is emitted by the compiler, and a dedicated > brk handler is used to print bug reports. > > -A potential expansion of this mode is a hardware tag-based mode, which would > -use hardware memory tagging support instead of compiler instrumentation and > -manual shadow memory manipulation. > +Software tag-based KASAN uses 0xFF as a match-all pointer tag (accesses through > +pointers with 0xFF pointer tag aren't checked). The value 0xFE is currently > +reserved to tag freed memory regions. > + > +Software tag-based KASAN currently only supports tagging of slab memory. > + > +Hardware tag-based KASAN > +~~~~~~~~~~~~~~~~~~~~~~~~ > + > +Hardware tag-based KASAN is similar to the software mode in concept, but uses > +hardware memory tagging support instead of compiler instrumentation and > +shadow memory. > + > +Hardware tag-based KASAN is currently only implemented for arm64 architecture > +and based on both arm64 Memory Tagging Extension (MTE) introduced in ARMv8.5 > +Instruction Set Architecture, and Top Byte Ignore (TBI). > + > +Special arm64 instructions are used to assign memory tags for each allocation. > +Same tags are assigned to pointers to those allocations. On every memory > +access, hardware makes sure that tag of the memory that is being accessed is > +equal to tag of the pointer that is used to access this memory. In case of a > +tag mismatch a fault is generated and a report is printed. > + > +Hardware tag-based KASAN uses 0xFF as a match-all pointer tag (accesses through > +pointers with 0xFF pointer tag aren't checked). The value 0xFE is currently > +reserved to tag freed memory regions. > + > +Hardware tag-based KASAN currently only supports tagging of slab memory. > > What memory accesses are sanitised by KASAN? > -------------------------------------------- > -- > 2.28.0.681.g6f77f65b4e-goog > 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=-11.2 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_SANE_1 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 EB996C4727E for ; Thu, 1 Oct 2020 18:05:35 +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 5FA8820848 for ; Thu, 1 Oct 2020 18:05:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="2YJK+p9n"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=google.com header.i=@google.com header.b="dPA+Od53" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5FA8820848 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:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=hFV98sYtbfDNS/5MjmgtQ92XH3qxzLaUQ2bxHh8Dwc0=; b=2YJK+p9nWgl7WReTfN/CFbJij oaBNbJNwDAIKXG4n0EmNLZMx9UWlVFbHPfIa1FTj5ce4pofHVD/8bRXwKf5hZgXZ9RI844G2FOW+J Btb7KSpE3Lx0Z+ZByFHqSyYBZBqRwhFuedg3ZcmxP2TXcbYzC71j7pvqcPw/L5/CTAKOM9LTdQrcW odHrlS5OmO4huXZ1Bxotft76mT2pkewTe7r7BeWXtoSBtm0J+MdGQg6A6yonIrjuEWwhxu/SZTGCx 3WJ5yK4eORTHu1y3FvpcCuy7chC3IYj0HbuZPUdtLuzC7JiYFvJWjVh+MFw//KqNE14Q0WqxjSYNQ SO7T7tBFA==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kO2w4-0001IT-9q; Thu, 01 Oct 2020 18:04:08 +0000 Received: from mail-wr1-x444.google.com ([2a00:1450:4864:20::444]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kO2w1-0001HQ-6J for linux-arm-kernel@lists.infradead.org; Thu, 01 Oct 2020 18:04:06 +0000 Received: by mail-wr1-x444.google.com with SMTP id z4so6872521wrr.4 for ; Thu, 01 Oct 2020 11:04:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=0OdyXaVNiyIQMSnkmN1U5DBWCyVDZmuQfjlNhLtDrKs=; b=dPA+Od53q5f/HBtQwvz6tXehIq+teMdNnK314CY3s0ajOt31vt/u/6D54Q/Ix/LC86 VtbYmG/LRaO//ScEveC5LTytEFM1+3pyoHPWuviFMpXhjPErq3Ufy2aSE62Z1E54Jr6x fqWFaqqQi3HGXr9rIfyLZrmvxYUAsZ3HsNF8y8akiDP5oppHmkSq2PJk0baeSBr0X0ou AUH/o1uBlIATCN1Px1ykRaBmK5Mn1QE0VhyzivGl4dPLnU2lDdrakcyrmDF6NyYXkxzN SJIsUNhdD1tp2kvB482PCt/cq9B2r/JGgCl6SNVrMLV76ZijAIXnbqO8oNjGq3WyT6CK Rs/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=0OdyXaVNiyIQMSnkmN1U5DBWCyVDZmuQfjlNhLtDrKs=; b=N6K3wciODTXRo6f7Sejb/L1Xfzj4jMIyZQEFk5X4Qie+QfHBQ5QWZX+MVIM/rDH+b+ eZ9y2rFsIBMX6qXoD26i+FET2lm4Sezk1iflVxLD0Tj2ISeDevmtLOV9+ATO5EZVKFGH ReEzJgCGPluJ16/ED0bZ8eZVyBInC1e1Shh9hx5aEdqzJ1Q2OKevW7pA0v2lriHI/uUG WuMddiQOKMxl+zGKaWtqB6KZugRfN+7chfPH1v+kS7Vd77krn+VULT+COwfvtiHqd2bX 9O7uU/IQAkOHEZFWD8tgHXkiH7oGpxFQVfC+YqV7b+xwyfpwTPROXGBX8tjXvl1NPXo8 lT2g== X-Gm-Message-State: AOAM530RKg7v5M6b6YzxNBBWG+ib5r7Vgm9D6AnUHGhH0E87SF8B4p8m dK7lQUIu78JP6c0TBba7PrXi4w== X-Google-Smtp-Source: ABdhPJwzl9G8I0FIwZnl+qK3rpBAlZVN5JVj57b7Bi+4u6kcK9IXkcXgdVGaQG1V73bZU6YmgI5YXQ== X-Received: by 2002:adf:e4cf:: with SMTP id v15mr10259531wrm.174.1601575443811; Thu, 01 Oct 2020 11:04:03 -0700 (PDT) Received: from elver.google.com ([100.105.32.75]) by smtp.gmail.com with ESMTPSA id k6sm950946wmf.30.2020.10.01.11.04.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 01 Oct 2020 11:04:03 -0700 (PDT) Date: Thu, 1 Oct 2020 20:03:57 +0200 From: elver@google.com To: Andrey Konovalov Subject: Re: [PATCH v3 39/39] kasan: add documentation for hardware tag-based mode Message-ID: <20201001180357.GW4162920@elver.google.com> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.14.5 (2020-06-23) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201001_140405_250816_91AB43DC X-CRM114-Status: GOOD ( 34.32 ) 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: linux-arm-kernel@lists.infradead.org, Branislav Rankov , Elena Petrova , Catalin Marinas , Kevin Brodsky , Will Deacon , linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, linux-mm@kvack.org, Alexander Potapenko , Evgenii Stepanov , Andrey Ryabinin , Andrew Morton , Vincenzo Frascino , Dmitry Vyukov 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 Fri, Sep 25, 2020 at 12:50AM +0200, Andrey Konovalov wrote: > Add documentation for hardware tag-based KASAN mode and also add some > clarifications for software tag-based mode. > > Signed-off-by: Andrey Konovalov > Signed-off-by: Vincenzo Frascino Reviewed-by: Marco Elver > --- > Change-Id: Ib46cb444cfdee44054628940a82f5139e10d0258 > --- > Documentation/dev-tools/kasan.rst | 78 ++++++++++++++++++++++--------- > 1 file changed, 57 insertions(+), 21 deletions(-) > > diff --git a/Documentation/dev-tools/kasan.rst b/Documentation/dev-tools/kasan.rst > index a3030fc6afe5..d2d47c82a7b9 100644 > --- a/Documentation/dev-tools/kasan.rst > +++ b/Documentation/dev-tools/kasan.rst > @@ -5,12 +5,14 @@ Overview > -------- > > KernelAddressSANitizer (KASAN) is a dynamic memory error detector designed to > -find out-of-bound and use-after-free bugs. KASAN has two modes: generic KASAN > -(similar to userspace ASan) and software tag-based KASAN (similar to userspace > -HWASan). > +find out-of-bound and use-after-free bugs. KASAN has three modes: > +1. generic KASAN (similar to userspace ASan), > +2. software tag-based KASAN (similar to userspace HWASan), > +3. hardware tag-based KASAN (based on hardware memory tagging). > > -KASAN uses compile-time instrumentation to insert validity checks before every > -memory access, and therefore requires a compiler version that supports that. > +Software KASAN modes (1 and 2) use compile-time instrumentation to insert > +validity checks before every memory access, and therefore require a compiler > +version that supports that. > > Generic KASAN is supported in both GCC and Clang. With GCC it requires version > 8.3.0 or later. With Clang it requires version 7.0.0 or later, but detection of > @@ -19,7 +21,7 @@ out-of-bounds accesses for global variables is only supported since Clang 11. > Tag-based KASAN is only supported in Clang and requires version 7.0.0 or later. > > Currently generic KASAN is supported for the x86_64, arm64, xtensa, s390 and > -riscv architectures, and tag-based KASAN is supported only for arm64. > +riscv architectures, and tag-based KASAN modes are supported only for arm64. > > Usage > ----- > @@ -28,14 +30,16 @@ To enable KASAN configure kernel with:: > > CONFIG_KASAN = y > > -and choose between CONFIG_KASAN_GENERIC (to enable generic KASAN) and > -CONFIG_KASAN_SW_TAGS (to enable software tag-based KASAN). > +and choose between CONFIG_KASAN_GENERIC (to enable generic KASAN), > +CONFIG_KASAN_SW_TAGS (to enable software tag-based KASAN), and > +CONFIG_KASAN_HW_TAGS (to enable hardware tag-based KASAN). > > -You also need to choose between CONFIG_KASAN_OUTLINE and CONFIG_KASAN_INLINE. > -Outline and inline are compiler instrumentation types. The former produces > -smaller binary while the latter is 1.1 - 2 times faster. > +For software modes, you also need to choose between CONFIG_KASAN_OUTLINE and > +CONFIG_KASAN_INLINE. Outline and inline are compiler instrumentation types. > +The former produces smaller binary while the latter is 1.1 - 2 times faster. > > -Both KASAN modes work with both SLUB and SLAB memory allocators. > +Both software KASAN modes work with both SLUB and SLAB memory allocators, > +hardware tag-based KASAN currently only support SLUB. > For better bug detection and nicer reporting, enable CONFIG_STACKTRACE. > > To augment reports with last allocation and freeing stack of the physical page, > @@ -196,17 +200,24 @@ and the second to last. > Software tag-based KASAN > ~~~~~~~~~~~~~~~~~~~~~~~~ > > -Tag-based KASAN uses the Top Byte Ignore (TBI) feature of modern arm64 CPUs to > -store a pointer tag in the top byte of kernel pointers. Like generic KASAN it > -uses shadow memory to store memory tags associated with each 16-byte memory > +Software tag-based KASAN requires software memory tagging support in the form > +of HWASan-like compiler instrumentation (see HWASan documentation for details). > + > +Software tag-based KASAN is currently only implemented for arm64 architecture. > + > +Software tag-based KASAN uses the Top Byte Ignore (TBI) feature of arm64 CPUs > +to store a pointer tag in the top byte of kernel pointers. Like generic KASAN > +it uses shadow memory to store memory tags associated with each 16-byte memory > cell (therefore it dedicates 1/16th of the kernel memory for shadow memory). > > -On each memory allocation tag-based KASAN generates a random tag, tags the > -allocated memory with this tag, and embeds this tag into the returned pointer. > +On each memory allocation software tag-based KASAN generates a random tag, tags > +the allocated memory with this tag, and embeds this tag into the returned > +pointer. > + > Software tag-based KASAN uses compile-time instrumentation to insert checks > before each memory access. These checks make sure that tag of the memory that > is being accessed is equal to tag of the pointer that is used to access this > -memory. In case of a tag mismatch tag-based KASAN prints a bug report. > +memory. In case of a tag mismatch software tag-based KASAN prints a bug report. > > Software tag-based KASAN also has two instrumentation modes (outline, that > emits callbacks to check memory accesses; and inline, that performs the shadow > @@ -215,9 +226,34 @@ simply printed from the function that performs the access check. With inline > instrumentation a brk instruction is emitted by the compiler, and a dedicated > brk handler is used to print bug reports. > > -A potential expansion of this mode is a hardware tag-based mode, which would > -use hardware memory tagging support instead of compiler instrumentation and > -manual shadow memory manipulation. > +Software tag-based KASAN uses 0xFF as a match-all pointer tag (accesses through > +pointers with 0xFF pointer tag aren't checked). The value 0xFE is currently > +reserved to tag freed memory regions. > + > +Software tag-based KASAN currently only supports tagging of slab memory. > + > +Hardware tag-based KASAN > +~~~~~~~~~~~~~~~~~~~~~~~~ > + > +Hardware tag-based KASAN is similar to the software mode in concept, but uses > +hardware memory tagging support instead of compiler instrumentation and > +shadow memory. > + > +Hardware tag-based KASAN is currently only implemented for arm64 architecture > +and based on both arm64 Memory Tagging Extension (MTE) introduced in ARMv8.5 > +Instruction Set Architecture, and Top Byte Ignore (TBI). > + > +Special arm64 instructions are used to assign memory tags for each allocation. > +Same tags are assigned to pointers to those allocations. On every memory > +access, hardware makes sure that tag of the memory that is being accessed is > +equal to tag of the pointer that is used to access this memory. In case of a > +tag mismatch a fault is generated and a report is printed. > + > +Hardware tag-based KASAN uses 0xFF as a match-all pointer tag (accesses through > +pointers with 0xFF pointer tag aren't checked). The value 0xFE is currently > +reserved to tag freed memory regions. > + > +Hardware tag-based KASAN currently only supports tagging of slab memory. > > What memory accesses are sanitised by KASAN? > -------------------------------------------- > -- > 2.28.0.681.g6f77f65b4e-goog > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel