Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp1855196pxb; Sat, 14 Nov 2020 04:52:49 -0800 (PST) X-Google-Smtp-Source: ABdhPJyafsvigGTULKq6vTkRw+THDnWsxI6ZPBIS7tjSv/nqNn/ANytZ7Ms98zo5gyw4KLyj3fog X-Received: by 2002:a50:e041:: with SMTP id g1mr7289591edl.385.1605358368921; Sat, 14 Nov 2020 04:52:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605358368; cv=none; d=google.com; s=arc-20160816; b=YrrYmhNgcl+MiFRWfJxf4GIvp2BY8mg3vhR8T13ik7ik6Gmt1AeeqJLe8z4NFA84iA d9pQ8zlL/vBPeYwizAeYLkoN2gcgJh9JV+fTrvjOnJCyqloATyO2vSIJxgp8aNqrSi5T nIOzKHnalnJMBwnufwaEf1Q+CkzO/6/kwZCaVJPp/aAGXRFu7qsSZJ3rjfO+lLMsQpYp iiPoIsB0NoxqEjs0H9kI8m5hkL1lQpt7qxrK7J5sRUC/cADbv+8/FrFZNQWNCpecZbPE bmxDYo1/BHDtYfpZtAm1JKgsGXThVEeT9QBZUWD305CNcqNQHxUCkX9r3zsh4J8qrd5o LG1g== 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=RRZnlUL5iDro+Y08Pj657BeeXVmfKvVP4SXWMzxw9Ck=; b=vMmz1JOaId47IPgWTsJ6LSGuO4lYzZQv1Px6BENmnbaFJAnSnhtviveY0lsaVyIb54 VoLh3blobN7Rryof/ovy0ris3S73G3YhYkCNj0bYGyYL2t5+TCLKsDWAynEjQB7BMPOR yYG/isbu2or87qxy5ek4npEqM1x0zibIyc+6gt9RC+Mz1JJ+EMd1iLPVCZjpzt24sYqD irVMOGrqZph2wzc8q/a0nTuIMmHlIbwmOV9l3b84bHNpW0idtfsR99ioHCClmD6if+Um AeDad0IwKbHfPYLVYTYlbQL83SZu6hR0vtcXYuEVNJvNh4sAPtH6ZVwQxA8aJsa03Adp frMA== 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 u14si8574279edq.494.2020.11.14.04.52.25; Sat, 14 Nov 2020 04:52:48 -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 S1726725AbgKNMsB (ORCPT + 99 others); Sat, 14 Nov 2020 07:48:01 -0500 Received: from mail.kernel.org ([198.145.29.99]:41174 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726112AbgKNMsB (ORCPT ); Sat, 14 Nov 2020 07:48:01 -0500 Received: from gaia (unknown [2.26.170.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 804B82222C; Sat, 14 Nov 2020 12:47:58 +0000 (UTC) Date: Sat, 14 Nov 2020 12:47:56 +0000 From: Catalin Marinas To: Andrey Konovalov Cc: Andrew Morton , Will Deacon , Vincenzo Frascino , Dmitry Vyukov , Andrey Ryabinin , Alexander Potapenko , Marco Elver , Evgenii Stepanov , Branislav Rankov , Kevin Brodsky , kasan-dev@googlegroups.com, linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH mm v10 28/42] arm64: kasan: Allow enabling in-kernel MTE Message-ID: <20201114124755.GD2837@gaia> References: <123c654a82018611d38af8c83d1e90c16558ce52.1605305705.git.andreyknvl@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <123c654a82018611d38af8c83d1e90c16558ce52.1605305705.git.andreyknvl@google.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 13, 2020 at 11:15:56PM +0100, Andrey Konovalov wrote: > From: Vincenzo Frascino > > Hardware tag-based KASAN relies on Memory Tagging Extension (MTE) > feature and requires it to be enabled. MTE supports > > This patch adds a new mte_enable_kernel() helper, that enables MTE in > Synchronous mode in EL1 and is intended to be called from KASAN runtime > during initialization. > > The Tag Checking operation causes a synchronous data abort as > a consequence of a tag check fault when MTE is configured in > synchronous mode. > > As part of this change enable match-all tag for EL1 to allow the > kernel to access user pages without faulting. This is required because > the kernel does not have knowledge of the tags set by the user in a > page. > > Note: For MTE, the TCF bit field in SCTLR_EL1 affects only EL1 in a > similar way as TCF0 affects EL0. > > MTE that is built on top of the Top Byte Ignore (TBI) feature hence we > enable it as part of this patch as well. > > Signed-off-by: Vincenzo Frascino > Co-developed-by: Andrey Konovalov > Signed-off-by: Andrey Konovalov Reviewed-by: Catalin Marinas