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>,
	Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>
Subject: [GIT PULL] locking changes for v6.1
Date: Fri, 7 Oct 2022 10:12:13 +0200	[thread overview]
Message-ID: <Yz/fXafXBApgFQrF@gmail.com> (raw)

Linus,

Please pull the latest locking/core git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-core-2022-10-07

   # HEAD: 76e64c73db9542ff4bae8a60f4f32e38f3799b95 locking/lockdep: Print more debug information - report name and key when look_up_lock_class() got confused

Locking changes for v6.1:

 - Disable preemption in rwsem_write_trylock()'s attempt to
   take the rwsem, to avoid RT tasks hogging the CPU, which
   managed to preempt this function after the owner has
   been cleared but before a new owner is set. Also add
   debug checks to enforce this.

 - Add __lockfunc to more slow path functions and add
   __sched to semaphore functions.

 - Mark spinlock APIs noinline when the respective CONFIG_INLINE_SPIN_*
   toggles are disabled, to reduce LTO text size.

 - Print more debug information when lockdep gets confused
   in look_up_lock_class().

 - Improve header file abuse checks.

 - Misc cleanups

 Thanks,

	Ingo

------------------>
Andi Kleen (1):
      locking/spinlocks: Mark spinlocks noinline when inline spinlocks are disabled

Gokul krishna Krishnakumar (1):
      locking/rwsem: Disable preemption while trying for rwsem lock

Namhyung Kim (2):
      locking: Add __lockfunc to slow path functions
      locking: Add __sched to semaphore functions

Sebastian Andrzej Siewior (1):
      locking: Detect includes rwlock.h outside of spinlock.h

Slark Xiao (1):
      selftests: futex: Fix 'the the' typo in comment

Tetsuo Handa (1):
      locking/lockdep: Print more debug information - report name and key when look_up_lock_class() got confused


 arch/x86/include/asm/qspinlock_paravirt.h          | 13 ++---
 include/linux/rwlock.h                             |  2 +-
 include/linux/spinlock.h                           |  2 +
 include/linux/spinlock_api_smp.h                   |  2 +-
 include/linux/spinlock_api_up.h                    |  2 +-
 include/linux/spinlock_rt.h                        |  2 +-
 include/linux/spinlock_up.h                        |  2 +-
 kernel/locking/lockdep.c                           |  6 ++-
 kernel/locking/qrwlock.c                           |  4 +-
 kernel/locking/qspinlock.c                         |  2 +-
 kernel/locking/qspinlock_paravirt.h                |  4 +-
 kernel/locking/rwsem.c                             | 14 +++++-
 kernel/locking/semaphore.c                         | 12 ++---
 kernel/locking/spinlock.c                          | 56 +++++++++++-----------
 .../functional/futex_requeue_pi_signal_restart.c   |  2 +-
 15 files changed, 70 insertions(+), 55 deletions(-)

             reply	other threads:[~2022-10-07  8:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07  8:12 Ingo Molnar [this message]
2022-10-10 17:22 ` [GIT PULL] locking changes for v6.1 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=Yz/fXafXBApgFQrF@gmail.com \
    --to=mingo@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@kernel.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.