All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] locking/debug updates for v5.15
Date: Wed, 1 Sep 2021 08:31:10 +0200	[thread overview]
Message-ID: <YS8eLmLdB7a9WLGd@gmail.com> (raw)

Linus,

Please pull the latest locking/debug git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-debug-2021-09-01

   # HEAD: 4812c9111220b0af00f7a436cc02ffaed289962c Merge branch 'lkmm' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu into locking/debug

LKMM updates:

 - Update documentation and code example

KCSAN updates:

 - Introduce CONFIG_KCSAN_STRICT (which RCU uses)
 - Optimize use of get_ctx() by kcsan_found_watchpoint()
 - Rework atomic.h into permissive.h
 - Add the ability to ignore writes that change only one bit of a given data-racy variable.
 - Improve comments

 Thanks,

	Ingo

------------------>
Manfred Spraul (1):
      tools/memory-model: Heuristics using data_race() must handle all values

Marco Elver (8):
      kcsan: Improve some Kconfig comments
      kcsan: Remove CONFIG_KCSAN_DEBUG
      kcsan: Introduce CONFIG_KCSAN_STRICT
      kcsan: Reduce get_ctx() uses in kcsan_found_watchpoint()
      kcsan: Rework atomic.h into permissive.h
      kcsan: Print if strict or non-strict during init
      kcsan: permissive: Ignore data-racy 1-bit value changes
      kcsan: Make strict mode imply interruptible watchers

Paul E. McKenney (3):
      tools/memory-model: Make read_foo_diagnostic() more clearly diagnostic
      tools/memory-model: Add example for heuristic lockless reads
      tools/memory-model: Document data_race(READ_ONCE())


 Documentation/dev-tools/kcsan.rst                  |  12 ++
 kernel/kcsan/atomic.h                              |  23 ----
 kernel/kcsan/core.c                                |  77 +++++++----
 kernel/kcsan/kcsan_test.c                          |  32 +++++
 kernel/kcsan/permissive.h                          |  94 +++++++++++++
 lib/Kconfig.kcsan                                  |  42 ++++--
 .../memory-model/Documentation/access-marking.txt  | 151 ++++++++++++++++++---
 7 files changed, 352 insertions(+), 79 deletions(-)
 delete mode 100644 kernel/kcsan/atomic.h
 create mode 100644 kernel/kcsan/permissive.h

             reply	other threads:[~2021-09-01  6:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01  6:31 Ingo Molnar [this message]
2021-09-02 20:05 ` [GIT PULL] locking/debug updates for v5.15 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=YS8eLmLdB7a9WLGd@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.