Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp5208456pxj; Wed, 9 Jun 2021 11:43:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzmKwtB+JcOiFmv+HpUmCX4syZavBpDniecw/cCrOpFRkuh3Sz7Ezhaar/rMECtXc8TjQp4 X-Received: by 2002:aa7:cf0d:: with SMTP id a13mr775535edy.384.1623264228841; Wed, 09 Jun 2021 11:43:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623264228; cv=none; d=google.com; s=arc-20160816; b=VQR6yl58lGwaf12Q1dd2atcOKrQMAidIh4iAALkFXr/Zvqx6W4m0w0VexlO+pdinCw eATM4PUVpAoguO0bhIv0NMwwssXJ8TONq6vgYLu9pjyCNVYuTMAcdx41Yqx3rd8t2GnQ HTS9cSXIWJUPgYL6t4DRyBN5P4NRx79K2yxjBi5vzdyhLgrvVEDAkJju1jaermwzCBDq pfoQWzSDXVTZ6gLlyZQuj7sMm+Mo7bj/mNLmAtGWene8eqaTwrhXLOo+EFHByOGnfnvq z9grQuyIE1ljo8/1b6wlyoO0lh+ebXKa4Eb4gHvqaFg4vBmJEETY8cgtfQKdNRC6Aveh m+rw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:references:in-reply-to:message-id:date:subject :cc:to:from; bh=32Ni2Giim5j3kTbiI5Ajhwkw5DPj4hyxaap2mNZS5ac=; b=H5xsxb5Kkkd91HtEYQ8DB89K/qc4EEMBe/39eouCOtEiko0OwETtbhjyRwZiCsi2Dn qBx/dRwvBlFDcPs32tIISVU3fm3YptIPkrnGtrTTMEs1KbTDEPZE50MUmOcp4QZvs0jB zYWGWVb+ukcWUwQ3HOyfHw+jlZ4DhKARWJ5SfwOOmaHMjvvI6hei8DZpFIf9yawMbEdj 3lf2ScCEL7edEMzNM7djXNbc3YjG5OufiN1nBBnMt9tyHm6eNVbQfwek5UFkQIGzzYHh ll8TPa1U1aPiecvANe+ee4JBNlNBRtJIwR3jIs9pISy2zL6QnnkFdt1BCtBsY4j9eAz2 V+tQ== 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 24si410565edv.59.2021.06.09.11.43.24; Wed, 09 Jun 2021 11:43:48 -0700 (PDT) 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 S235475AbhFIMWN (ORCPT + 99 others); Wed, 9 Jun 2021 08:22:13 -0400 Received: from foss.arm.com ([217.140.110.172]:58426 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235456AbhFIMWH (ORCPT ); Wed, 9 Jun 2021 08:22:07 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 32C6E101E; Wed, 9 Jun 2021 05:20:13 -0700 (PDT) Received: from lakrids.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 16DA13F73D; Wed, 9 Jun 2021 05:20:09 -0700 (PDT) From: Mark Rutland To: linux-kernel@vger.kernel.org Cc: benh@kernel.crashing.org, boqun.feng@gmail.com, bp@alien8.de, catalin.marinas@arm.com, dvyukov@google.com, elver@google.com, ink@jurassic.park.msu.ru, jonas@southpole.se, juri.lelli@redhat.com, linux@armlinux.org.uk, luto@kernel.org, mark.rutland@arm.com, mattst88@gmail.com, mingo@redhat.com, monstr@monstr.eu, mpe@ellerman.id.au, paulmck@kernel.org, paulus@samba.org, peterz@infradead.org, rth@twiddle.net, shorne@gmail.com, stefan.kristiansson@saunalahti.fi, tglx@linutronix.de, vincent.guittot@linaro.org, will@kernel.org Subject: [RFC PATCH 01/10] thread_info: add helpers to snapshot thread flags Date: Wed, 9 Jun 2021 13:19:52 +0100 Message-Id: <20210609122001.18277-2-mark.rutland@arm.com> X-Mailer: git-send-email 2.11.0 In-Reply-To: <20210609122001.18277-1-mark.rutland@arm.com> References: <20210609122001.18277-1-mark.rutland@arm.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org We have common helpers to manipulate individual thread flags, but where code wants to check several flags at once, it must open code reading current_thread_info()->flags and operating on a snapshot. As some flags can be set remotely it's necessary to use READ_ONCE() to get a consistent snapshot even when IRQs are disabled, but some code forgets to do this. Generally this is unlike to cause a problem in practice, but it is somewhat unsound, and KCSAN will legitimately warn that there is a data race. To make it easier to do the right thing, and to highlight that concurrent modification is possible, let's add a new helpers to snapshot the flags, which should be used in preference to plain reads. Subsequent patches will move existing code to use the new helpers. Signed-off-by: Mark Rutland Cc: Boqun Feng Cc: Dmitry Vyukov Cc: Marco Elver Cc: Paul E. McKenney Cc: Peter Zijlstra Cc: Will Deacon --- include/linux/thread_info.h | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/include/linux/thread_info.h b/include/linux/thread_info.h index 157762db9d4b..f3769842046d 100644 --- a/include/linux/thread_info.h +++ b/include/linux/thread_info.h @@ -117,6 +117,11 @@ static inline int test_ti_thread_flag(struct thread_info *ti, int flag) return test_bit(flag, (unsigned long *)&ti->flags); } +static inline unsigned long read_ti_thread_flags(struct thread_info *ti) +{ + return READ_ONCE(ti->flags); +} + #define set_thread_flag(flag) \ set_ti_thread_flag(current_thread_info(), flag) #define clear_thread_flag(flag) \ @@ -129,6 +134,11 @@ static inline int test_ti_thread_flag(struct thread_info *ti, int flag) test_and_clear_ti_thread_flag(current_thread_info(), flag) #define test_thread_flag(flag) \ test_ti_thread_flag(current_thread_info(), flag) +#define read_thread_flags() \ + read_ti_thread_flags(current_thread_info()) + +#define read_task_thread_flags(t) \ + read_ti_thread_flags(task_thread_info(t)) #ifdef CONFIG_GENERIC_ENTRY #define set_syscall_work(fl) \ -- 2.11.0