From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
kernel-team@meta.com, elver@google.com,
penguin-kernel@i-love.sakura.ne.jp
Subject: [GIT PULL] KCSAN changes for v6.10
Date: Sun, 12 May 2024 10:33:08 -0700 [thread overview]
Message-ID: <ccdfb04f-9d2c-4033-a29c-bb9677fcbea5@paulmck-laptop> (raw)
Hello, Linus,
Once the v6.4 merge window opens, please pull the latest KCSAN git
commit from:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/kcsan.2024.05.10a
# HEAD: 31f605a308e627f06e4e6ab77254473f1c90f0bf: kcsan, compiler_types: Introduce __data_racy type qualifier (2024-05-07 11:39:50 -0700)
----------------------------------------------------------------
kcsan: Introduce __data_racy type qualifier
This commit adds a __data_racy type qualifier that enables kernel
developers to inform KCSAN that a given variable is a shared variable
without needing to mark each and every access. This allows pre-KCSAN
code to be correctly (if approximately) instrumented withh very little
effort, and also provides people reading the code a clear indication that
the variable is in fact shared. In addition, it permits incremental
transition to per-access KCSAN marking, so that (for example) a given
subsystem can be transitioned one variable at a time, while avoiding
large numbers of KCSAN warnings during this transition.
----------------------------------------------------------------
Marco Elver (1):
kcsan, compiler_types: Introduce __data_racy type qualifier
Documentation/dev-tools/kcsan.rst | 10 ++++++++++
include/linux/compiler_types.h | 7 +++++++
kernel/kcsan/kcsan_test.c | 17 +++++++++++++++++
3 files changed, 34 insertions(+)
next reply other threads:[~2024-05-12 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 17:33 Paul E. McKenney [this message]
2024-05-13 17:27 ` [GIT PULL] KCSAN changes for v6.10 pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ccdfb04f-9d2c-4033-a29c-bb9677fcbea5@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).