Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1329755pxf; Fri, 12 Mar 2021 07:16:21 -0800 (PST) X-Google-Smtp-Source: ABdhPJyQ5m1IyVVSy2U7eDGpS/+GIH8i0ehNmdu6CeKLX6FjlLvFRCTYVuiaQqWQJ/I8gX2mKN+K X-Received: by 2002:a05:6402:5189:: with SMTP id q9mr14561802edd.168.1615562181563; Fri, 12 Mar 2021 07:16:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1615562181; cv=none; d=google.com; s=arc-20160816; b=kPrhQfc7XEs32ATBcvRQMYobOBtHWfjtXYhYeL84B1Q1uD+S6gdXwSjxx6z82zKGMM w8/1ih7aTW/+KuZ8WpmfOpTMbBg+V7qBIODLRsNBsOVpngmsatgzPodRhySbCzuk1R68 03JjBOF7Gvw1kgjv0wJtSJNuVQH5Nnkq5WhSK8AFYWIi1vE5bRLntT7oBnLF7S8ePtkv QToc0T4h3EUegNXXuPakMe+3ocLb8fdmOJHuC6P4N9xvTKKkyrMXg3hDjQZ3GfP+u3WJ eo3Pm08enPpmHgZNUKveapCSfiel1WoXBo+O43+Xp/8MQXAnPHcvC9l/W8J+RBtkrj/3 8irA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=Ccjqmn5upCCbJjsnfIvzmRE3ELG2dQGUsyy8B0/QfJQ=; b=y3VcJibDvdONcF3a76U/jp89FKh5Ofmpr6b84Q7OIPMiPMQ1TdrMjVdXZYNuiWt+b2 2dMlSYEiQTbYAK/NzqHfGBOfPo8jAcUGxsAbkQvQ/OjDrkgN2GNmKc/snTfclT/qOJnt 73rGfeZYOV/InShAMisKWV4CArhkO1u+ORBCyx1J74z8qmTxjJpSc36y9rHzzChCTge2 j/WcHnzudKmnzbRO7GIUpHcgnVHQ10CEkxfobCDqorh4Ev91eXElN7auvI4ky0BYmnMB XQVMAGTxQaSS3OSUkOXhw/2AJMHlQtNfHH+qAUwUj976Za75aU1GlGAZkZ+Rm5Cv/XLH uXFw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q3si4081557eji.445.2021.03.12.07.15.49; Fri, 12 Mar 2021 07:16:21 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232136AbhCLPNL (ORCPT + 99 others); Fri, 12 Mar 2021 10:13:11 -0500 Received: from mail.kernel.org ([198.145.29.99]:45746 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232032AbhCLPNF (ORCPT ); Fri, 12 Mar 2021 10:13:05 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id A5C7964FD9; Fri, 12 Mar 2021 15:13:02 +0000 (UTC) Date: Fri, 12 Mar 2021 15:13:00 +0000 From: Catalin Marinas To: Vincenzo Frascino Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, Andrew Morton , Will Deacon , Dmitry Vyukov , Andrey Ryabinin , Alexander Potapenko , Marco Elver , Evgenii Stepanov , Branislav Rankov , Andrey Konovalov , Lorenzo Pieralisi Subject: Re: [PATCH v15 5/8] arm64: mte: Enable TCO in functions that can read beyond buffer limits Message-ID: <20210312151259.GB24210@arm.com> References: <20210312142210.21326-1-vincenzo.frascino@arm.com> <20210312142210.21326-6-vincenzo.frascino@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210312142210.21326-6-vincenzo.frascino@arm.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 12, 2021 at 02:22:07PM +0000, Vincenzo Frascino wrote: > diff --git a/arch/arm64/include/asm/mte.h b/arch/arm64/include/asm/mte.h > index 9b557a457f24..8603c6636a7d 100644 > --- a/arch/arm64/include/asm/mte.h > +++ b/arch/arm64/include/asm/mte.h > @@ -90,5 +90,20 @@ static inline void mte_assign_mem_tag_range(void *addr, size_t size) > > #endif /* CONFIG_ARM64_MTE */ > > +#ifdef CONFIG_KASAN_HW_TAGS > +/* Whether the MTE asynchronous mode is enabled. */ > +DECLARE_STATIC_KEY_FALSE(mte_async_mode); > + > +static inline bool system_uses_mte_async_mode(void) > +{ > + return static_branch_unlikely(&mte_async_mode); > +} > +#else > +static inline bool system_uses_mte_async_mode(void) > +{ > + return false; > +} > +#endif /* CONFIG_KASAN_HW_TAGS */ You can write this with fewer lines: DECLARE_STATIC_KEY_FALSE(mte_async_mode); static inline bool system_uses_mte_async_mode(void) { return IS_ENABLED(CONFIG_KASAN_HW_TAGS) && static_branch_unlikely(&mte_async_mode); } The compiler will ensure that mte_async_mode is not referred when !CONFIG_KASAN_HW_TAGS and therefore doesn't need to be defined. > diff --git a/arch/arm64/kernel/mte.c b/arch/arm64/kernel/mte.c > index fa755cf94e01..9362928ba0d5 100644 > --- a/arch/arm64/kernel/mte.c > +++ b/arch/arm64/kernel/mte.c > @@ -26,6 +26,10 @@ u64 gcr_kernel_excl __ro_after_init; > > static bool report_fault_once = true; > > +/* Whether the MTE asynchronous mode is enabled. */ > +DEFINE_STATIC_KEY_FALSE(mte_async_mode); > +EXPORT_SYMBOL_GPL(mte_async_mode); Maybe keep these bracketed by #ifdef CONFIG_KASAN_HW_TAGS. I think the mte_enable_kernel_*() aren't needed either if KASAN_HW is disabled (you can do it with an additional patch). With these, you can add: Reviewed-by: Catalin Marinas