mirror of https://lore.kernel.org/lkml/
 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>,
	Thomas Gleixner <tglx@linutronix.de>,
	Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>
Subject: [GIT PULL] locking updates for v7.4
Date: Sun, 18 Oct 2026 11:45:10 +0200	[thread overview]
Message-ID: <atSVJgnfPWO35u2U@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-2026-10-18

for you to fetch changes up to 67e0eadd862616cb22145d6117b79b79c4ae48fe:

Locking updates:

 - In the refcount checking code, BUG() on UAF related errors if
   CONFIG_BUG_ON_DATA_CORRUPTION=y (Jann Horn)

 - Add {over,under}flow detection for local_interrupt_{enable,disable}()
   (Boqun Feng)

 - Add kunit test case for max local_interrupt_disable() nesting level
   (Boqun Feng)

 - Clarify comment (Boqun Feng)

 Thanks,

	Ingo

------------------>
Boqun Feng (3):
      irq: Add {over,under}flow detection for local_interrupt_{enable,disable}
      irq: Explain better on NMI_MASK overflow condition
      irq: Add max local_interrupt_disable() nesting level kunit test case

Jann Horn (1):
      refcount: Use CONFIG_BUG_ON_DATA_CORRUPTION for UAF-related errors


 include/linux/hardirq.h              |  2 +-
 include/linux/interrupt_rc.h         | 13 +++++++++++++
 kernel/irq/refcount_interrupt_test.c | 22 ++++++++++++++++++++++
 lib/refcount.c                       | 15 ++++++++++++---
 4 files changed, 48 insertions(+), 4 deletions(-)

                 reply	other threads:[~2026-10-18  9:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=atSVJgnfPWO35u2U@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=tglx@linutronix.de \
    --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 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®