From nobody Fri Feb 13 01:39:47 2026 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 425BC14D293; Tue, 4 Jun 2024 22:14:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1717539262; cv=none; b=fazv0gI/Z7Qbw1fxwCdDhUMmvQHWFMJqsMxEAyH76mGTKdRU09vA+1eq1MnVhNwt+ZH0H9y1uMIb2lAxTXBQB5bPEjLBEHfCYso8w0ywTYhTQmVv7FcgNagOVvyBz/4QtKtgQB0pFfNAv0Ne0Hmh+/Z8nyJd9pf7/kc/Qu6/Qcc= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1717539262; c=relaxed/simple; bh=ygTLP2T8slbXOZ6W4tEAKQMW6AwWve81xPXtxXbnv+8=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=ZqUnMZ+iCj7CBL8/CUPOp5zndm4+CaSeAtpb4GugVRKdtY7ar7aDQKp0GM4AE+rS2eqFLBBr7V3nSYRq01euKJeYNYfsrlOh2NOrpVV1y5/llq9J3oCNqB88HL4A52qeCeJazl2IqkR9zJp5YukFL4ItujHos5W58AVfNxpWfr8= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=WjooraZf; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="WjooraZf" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D8D0BC2BBFC; Tue, 4 Jun 2024 22:14:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1717539261; bh=ygTLP2T8slbXOZ6W4tEAKQMW6AwWve81xPXtxXbnv+8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=WjooraZfIwtaTfAywxDMSlOrkCdYYFPZ7+5wfes6MP1KqO38si2R1O9XoB4jYUwlI J2Og1gHtAjKOaLaem9ppYfWPpUW6DHxLJurJenD1JU0GwPT0qPeo41r7Adt9KjTFBq uEdit18/04o2B7B0UGOUDetssx5ohdr4k9ILzBK4BIeoGQZZ4sQHvhtovCmfzVr4ge 4w/XzbOT/rpklacUqKhO7et6liJdNLZPN2XuWQitcC1eXfb1LgfGCiMajbtqmqtrwU U1I2dzAIJHFXBvAK4TIq6MSjNGlpCynylrIDUKsexfQMgXhSpcILLF+mdyVTOUKvcf z2sAq1DrpvtQA== Received: by paulmck-ThinkPad-P17-Gen-1.home (Postfix, from userid 1000) id 81331CE3F26; Tue, 4 Jun 2024 15:14:21 -0700 (PDT) From: "Paul E. McKenney" To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, kernel-team@meta.com, mingo@kernel.org Cc: stern@rowland.harvard.edu, parri.andrea@gmail.com, will@kernel.org, peterz@infradead.org, boqun.feng@gmail.com, npiggin@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk, luc.maranget@inria.fr, akiyks@gmail.com, "Paul E. McKenney" , Marco Elver , Daniel Lustig , Joel Fernandes Subject: [PATCH memory-model 3/3] tools/memory-model: Add KCSAN LF mentorship session citation Date: Tue, 4 Jun 2024 15:14:19 -0700 Message-Id: <20240604221419.2370127-3-paulmck@kernel.org> X-Mailer: git-send-email 2.40.1 In-Reply-To: References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Add a citation to Marco's LF mentorship session presentation entitled "The Kernel Concurrency Sanitizer" [ paulmck: Apply Marco Elver feedback. ] Reported-by: Marco Elver Signed-off-by: Paul E. McKenney Cc: Alan Stern Cc: Andrea Parri Cc: Will Deacon Cc: Peter Zijlstra Cc: Boqun Feng Cc: Nicholas Piggin Cc: David Howells Cc: Jade Alglave Cc: Luc Maranget Cc: Akira Yokosawa Cc: Daniel Lustig Cc: Joel Fernandes Cc: Acked-by: Andrea Parri Acked-by: Marco Elver Reviewed-by: Akira Yokosawa --- tools/memory-model/Documentation/access-marking.txt | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/tools/memory-model/Documentation/access-marking.txt b/tools/me= mory-model/Documentation/access-marking.txt index 65778222183e3..f531b0837356b 100644 --- a/tools/memory-model/Documentation/access-marking.txt +++ b/tools/memory-model/Documentation/access-marking.txt @@ -6,7 +6,8 @@ normal accesses to shared memory, that is "normal" as in ac= cesses that do not use read-modify-write atomic operations. It also describes how to document these accesses, both with comments and with special assertions processed by the Kernel Concurrency Sanitizer (KCSAN). This discussion -builds on an earlier LWN article [1]. +builds on an earlier LWN article [1] and Linux Foundation mentorship +session [2]. =20 =20 ACCESS-MARKING OPTIONS @@ -31,7 +32,7 @@ example: WRITE_ONCE(a, b + data_race(c + d) + READ_ONCE(e)); =20 Neither plain C-language accesses nor data_race() (#1 and #2 above) place -any sort of constraint on the compiler's choice of optimizations [2]. +any sort of constraint on the compiler's choice of optimizations [3]. In contrast, READ_ONCE() and WRITE_ONCE() (#3 and #4 above) restrict the compiler's use of code-motion and common-subexpression optimizations. Therefore, if a given access is involved in an intentional data race, @@ -594,5 +595,8 @@ REFERENCES [1] "Concurrency bugs should fear the big bad data-race detector (part 2)" https://lwn.net/Articles/816854/ =20 -[2] "Who's afraid of a big bad optimizing compiler?" +[2] "The Kernel Concurrency Sanitizer" + https://www.linuxfoundation.org/webinars/the-kernel-concurrency-saniti= zer + +[3] "Who's afraid of a big bad optimizing compiler?" https://lwn.net/Articles/793253/ --=20 2.40.1