Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp413230pxb; Tue, 9 Feb 2021 03:45:47 -0800 (PST) X-Google-Smtp-Source: ABdhPJwjGVyQffoYxMecjgsoC8LbaZWOqjryuOjRRIjmhl20Os5XHWSLA5wMKavrbpFCtcJcXYzL X-Received: by 2002:a17:906:d935:: with SMTP id rn21mr21982249ejb.443.1612871147149; Tue, 09 Feb 2021 03:45:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612871147; cv=none; d=google.com; s=arc-20160816; b=KtcRzsixvlZRiQtNRpVL/NfHlXOFdpyimjBTQQxxRn83qw7w/qh+/oxFLEJTI/pfKJ rnosx0go4cVel0WAIuAnLCE8Y3pNvKG2Mmv2s0PiokqfRhonUBbsJ3M0tWuJJeGDCWG9 od0zfVHHA7Af9NRgPnUu6g/MeEQT2CCwZOzfGb22E55HQYVnaBnj4ZFyluPFKBud0R5X jLNiMdcmniJVSWw9yPgzIs7FNDRzMP3Nwzo18KzUg+o91DkMe8Ro0QStIcykdgoVrPeE xxfXGRVJk4PG85xeDZTBhGmOl776Tg28WYYju0wBBHxvcxOG9SX1vmn2SPPxV0Ztj2fD 8D4Q== 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=OGk1UKXMrdpr0BtQ4crHAjReUGTSxMSLPPs/GvSup50=; b=bNU/eot1cWfuaqjruyCW9dWGgw8wj9tGCFFnjeArRpmNJ9SYmV1W+ogMKlK3j5IRQ+ qi7vU/U76NRZWgL9API8RY8h5w5SDLFlFAMRGNTdoIEkRkQA9vI/1fz8fR3LbqxU0BKj h+mROQ9xAjTXV8SBNVM2AhNTs48UjQm775c5KKPDtIZ82xldTTLdiDTJv7Lo5p+rACNu 0OJmSVGXZIBrCTvrx0nzdGJjgtORo2gx66Z80hunBPVOr586S2djFBikWcy1YAfx+pLe sAib+43sXl9fUdJvmVZQYut4R9f6yn8f9PQ/RbDDlc5UNP2oKdHjSoq2DibyI4DnVpJX o7ig== 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 z5si14385665edp.368.2021.02.09.03.45.23; Tue, 09 Feb 2021 03:45:47 -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 S230327AbhBILmY (ORCPT + 99 others); Tue, 9 Feb 2021 06:42:24 -0500 Received: from mail.kernel.org ([198.145.29.99]:48992 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230239AbhBILfx (ORCPT ); Tue, 9 Feb 2021 06:35:53 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id E2DBB64E6C; Tue, 9 Feb 2021 11:35:08 +0000 (UTC) Date: Tue, 9 Feb 2021 11:35:06 +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 v12 4/7] arm64: mte: Enable TCO in functions that can read beyond buffer limits Message-ID: <20210209113505.GD1435@arm.com> References: <20210208165617.9977-1-vincenzo.frascino@arm.com> <20210208165617.9977-5-vincenzo.frascino@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210208165617.9977-5-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 Mon, Feb 08, 2021 at 04:56:14PM +0000, Vincenzo Frascino wrote: > diff --git a/arch/arm64/include/asm/uaccess.h b/arch/arm64/include/asm/uaccess.h > index 0deb88467111..f43d78aee593 100644 > --- a/arch/arm64/include/asm/uaccess.h > +++ b/arch/arm64/include/asm/uaccess.h > @@ -188,6 +188,21 @@ static inline void __uaccess_enable_tco(void) > ARM64_MTE, CONFIG_KASAN_HW_TAGS)); > } > > +/* Whether the MTE asynchronous mode is enabled. */ > +DECLARE_STATIC_KEY_FALSE(mte_async_mode); > + > +static inline void __uaccess_disable_tco_async(void) > +{ > + if (static_branch_unlikely(&mte_async_mode)) > + __uaccess_disable_tco(); > +} > + > +static inline void __uaccess_enable_tco_async(void) > +{ > + if (static_branch_unlikely(&mte_async_mode)) > + __uaccess_enable_tco(); > +} I would add a comment here along the lines of what's in the commit log: these functions disable tag checking only if in MTE async mode since the sync mode generates exceptions synchronously and the nofault or load_unaligned_zeropad can handle them. > + > static inline void uaccess_disable_privileged(void) > { > __uaccess_disable_tco(); > @@ -307,8 +322,10 @@ do { \ > do { \ > int __gkn_err = 0; \ > \ > + __uaccess_enable_tco_async(); \ > __raw_get_mem("ldr", *((type *)(dst)), \ > (__force type *)(src), __gkn_err); \ > + __uaccess_disable_tco_async(); \ > if (unlikely(__gkn_err)) \ > goto err_label; \ > } while (0) > @@ -379,9 +396,11 @@ do { \ > #define __put_kernel_nofault(dst, src, type, err_label) \ > do { \ > int __pkn_err = 0; \ > + __uaccess_enable_tco_async(); \ > \ Nitpick: for consistency with the __get_kernel_nofault() function, please move the empty line above __uaccess_enable_tco_async(). > __raw_put_mem("str", *((type *)(src)), \ > (__force type *)(dst), __pkn_err); \ > + __uaccess_disable_tco_async(); \ > if (unlikely(__pkn_err)) \ > goto err_label; \ > } while(0) [...] > diff --git a/arch/arm64/kernel/mte.c b/arch/arm64/kernel/mte.c > index 92078e1eb627..60531afc706e 100644 > --- a/arch/arm64/kernel/mte.c > +++ b/arch/arm64/kernel/mte.c > @@ -27,6 +27,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); > + > static void mte_sync_page_tags(struct page *page, pte_t *ptep, bool check_swap) > { > pte_t old_pte = READ_ONCE(*ptep); > @@ -170,6 +174,12 @@ void mte_enable_kernel_sync(void) > void mte_enable_kernel_async(void) > { > __mte_enable_kernel("asynchronous", SCTLR_ELx_TCF_ASYNC); > + > + /* > + * This function is called on each active smp core, we do not > + * to take cpu_hotplug_lock again. > + */ > + static_branch_enable_cpuslocked(&mte_async_mode); > } Do we need to disable mte_async_mode in mte_enable_kernel_sync()? I think currently that's only done at boot time but kasan may gain some run-time features and change the mode dynamically. -- Catalin