From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Heiko Carstens <hca@linux.ibm.com>
Subject: [GIT PULL] Core kernel bug handling infrastructure changes for v6.19
Date: Mon, 1 Dec 2025 12:45:04 +0100 [thread overview]
Message-ID: <aS1_wFqXNmDh84jJ@gmail.com> (raw)
Linus,
Please pull the latest core/bugs Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-bugs-2025-12-01
# HEAD: b0a848f4a47a91a6b4d9a9fd739d047254df5a91 x86/bugs: Make i386 use GENERIC_BUG_RELATIVE_POINTERS
[ MERGE NOTE: this pull request depends on you having
pulled the objtool-core-2025-12-01 tree already. If
you haven't yet then please disregard this pull
request. ]
Core kernel bug handling infrastructure changes for v6.19:
- Improve WARN(), which has vararg printf like arguments,
to work with the x86 #UD based WARN-optimizing infrastructure
by hiding the format in the bug_table and replacing this
first argument with the address of the bug-table entry,
while making the actual function that's called a UD1 instruction.
(Peter Zijlstra)
- Introduce the CONFIG_DEBUG_BUGVERBOSE_DETAILED Kconfig switch
(Ingo Molnar, s390 support by Heiko Carstens)
Fixes and cleanups:
- bugs/s390: Remove private WARN_ON() implementation (Heiko Carstens)
- <asm/bugs.h>: Make i386 use GENERIC_BUG_RELATIVE_POINTERS
(Peter Zijlstra)
Thanks,
Ingo
------------------>
Heiko Carstens (2):
bugs/s390: Use 'cond_str' in __EMIT_BUG()
bugs/s390: Remove private WARN_ON() implementation
Ingo Molnar (15):
bugs/core: Extend __WARN_FLAGS() with the 'cond_str' parameter
bugs/core: Pass down the condition string of WARN_ON_ONCE(cond) warnings to __WARN_FLAGS()
bugs/core: Introduce the CONFIG_DEBUG_BUGVERBOSE_DETAILED Kconfig switch
bugs/x86: Extend _BUG_FLAGS() with the 'cond_str' parameter
bugs/x86: Augment warnings output by concatenating 'cond_str' with the regular __FILE__ string in _BUG_FLAGS()
bugs/powerpc: Pass in 'cond_str' to BUG_ENTRY()
bugs/powerpc: Concatenate 'cond_str' with '__FILE__' in BUG_ENTRY(), to extend WARN_ON/BUG_ON output
bugs/LoongArch: Pass in 'cond_str' to __BUG_ENTRY()
bugs/LoongArch: Concatenate 'cond_str' with '__FILE__' in __BUG_ENTRY(), to extend WARN_ON/BUG_ON output
bugs/s390: Pass in 'cond_str' to __EMIT_BUG()
bugs/riscv: Pass in 'cond_str' to __BUG_FLAGS()
bugs/riscv: Concatenate 'cond_str' with '__FILE__' in __BUG_FLAGS(), to extend WARN_ON/BUG_ON output
bugs/parisc: Concatenate 'cond_str' with '__FILE__' in __WARN_FLAGS(), to extend WARN_ON/BUG_ON output
bugs/sh: Concatenate 'cond_str' with '__FILE__' in __WARN_FLAGS(), to extend WARN_ON/BUG_ON output
bugs/core: Reorganize fields in the first line of WARNING output, add ->comm[] output
Peter Zijlstra (14):
x86: Rework __bug_table helpers
bug: Add BUG_FORMAT infrastructure
bug: Clean up CONFIG_GENERIC_BUG_RELATIVE_POINTERS
bug: Add BUG_FORMAT_ARGS infrastructure
bug: Add report_bug_entry()
bug: Implement WARN_ON() using __WARN_FLAGS()
bug: Allow architectures to provide __WARN_printf()
x86/bug: Add BUG_FORMAT basics
x86/bug: Use BUG_FORMAT for DEBUG_BUGVERBOSE_DETAILED
x86_64/bug: Implement __WARN_printf()
x86/bug: Implement WARN_ONCE()
x86_64/bug: Inline the UD1
x86/bug: Fix BUG_FORMAT vs KASLR
x86/bugs: Make i386 use GENERIC_BUG_RELATIVE_POINTERS
arch/arm64/include/asm/bug.h | 2 +-
arch/loongarch/include/asm/bug.h | 27 ++++----
arch/parisc/include/asm/bug.h | 6 +-
arch/powerpc/include/asm/bug.h | 12 ++--
arch/riscv/include/asm/bug.h | 10 +--
arch/s390/include/asm/bug.h | 102 ++++++++++++---------------
arch/sh/include/asm/bug.h | 4 +-
arch/x86/Kconfig | 2 +-
arch/x86/entry/entry.S | 8 +++
arch/x86/include/asm/bug.h | 146 ++++++++++++++++++++++++++++++---------
arch/x86/kernel/static_call.c | 13 +++-
arch/x86/kernel/traps.c | 119 ++++++++++++++++++++++++++++---
include/asm-generic/bug.h | 80 +++++++++++++++------
include/linux/bug.h | 8 +++
kernel/panic.c | 16 +++--
lib/Kconfig.debug | 10 +++
lib/bug.c | 90 ++++++++++++++++++++----
17 files changed, 477 insertions(+), 178 deletions(-)
next reply other threads:[~2025-12-01 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 11:45 Ingo Molnar [this message]
2025-12-02 5:54 ` [GIT PULL] Core kernel bug handling infrastructure changes for v6.19 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=aS1_wFqXNmDh84jJ@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.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.