mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
	kasan-dev@googlegroups.com, elver@google.com,
	ryasuoka@redhat.com
Subject: [GIT PULL] KCSAN changes for v6.2
Date: Fri, 2 Dec 2022 17:23:43 -0800	[thread overview]
Message-ID: <20221203012343.GA1816460@paulmck-ThinkPad-P17-Gen-1> (raw)

Hello, Linus,

Please pull the latest KCSAN git tree from:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/kcsan.2022.12.02a
  # HEAD: 144b9152791ffcd038c3b63063999b25780060d8: kcsan: Fix trivial typo in Kconfig help comments (2022-10-18 15:07:33 -0700)

----------------------------------------------------------------
KCSAN updates for v6.2

This series adds instrumentation for memcpy(), memset(), and memmove() for
Clang v16+'s new function names that are used when the -fsanitize=thread
argument is given.  It also fixes objtool warnings from KCSAN's volatile
instrumentation, and fixes a pair of typos in a pair of Kconfig options'
help clauses.

----------------------------------------------------------------
Marco Elver (2):
      kcsan: Instrument memcpy/memset/memmove with newer Clang
      objtool, kcsan: Add volatile read/write instrumentation to whitelist

Ryosuke Yasuoka (1):
      kcsan: Fix trivial typo in Kconfig help comments

 kernel/kcsan/core.c   | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
 lib/Kconfig.kcsan     |  6 +++---
 tools/objtool/check.c | 10 ++++++++++
 3 files changed, 63 insertions(+), 3 deletions(-)

             reply	other threads:[~2022-12-03  1:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-03  1:23 Paul E. McKenney [this message]
2022-12-12 16:31 ` 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=20221203012343.GA1816460@paulmck-ThinkPad-P17-Gen-1 \
    --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=ryasuoka@redhat.com \
    --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

all inboxes | Powered by JetHome®