From: Peter Zijlstra <peterz@infradead.org>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org, kees@kernel.org,
acarmina@redhat.com, jpoimboe@kernel.org, mark.rutland@arm.com,
torvalds@linuxfoundation.org, maciej.wieczor-retman@intel.com
Subject: Re: [PATCH v2 08/12] x86/bug: Add BUG_FORMAT basics
Date: Tue, 25 Nov 2025 12:17:50 +0100 [thread overview]
Message-ID: <20251125111750.GS4067720@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20251110115757.980264454@infradead.org>
On Mon, Nov 10, 2025 at 12:46:41PM +0100, Peter Zijlstra wrote:
> Opt-in to BUG_FORMAT for x86_64, adjust the BUGTABLE helper and for
> now, just store NULL pointers.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> arch/x86/include/asm/bug.h | 31 +++++++++++++++++++++----------
> 1 file changed, 21 insertions(+), 10 deletions(-)
>
> --- a/arch/x86/include/asm/bug.h
> +++ b/arch/x86/include/asm/bug.h
> @@ -50,33 +50,44 @@
> #define __BUG_ENTRY_VERBOSE(file, line)
> #endif
>
> -#define __BUG_ENTRY(file, line, flags) \
> +#if defined(CONFIG_X86_64) || defined(CONFIG_DEBUG_BUGVERBOSE_DETAILED)
> +#define HAVE_ARCH_BUG_FORMAT
> +#define __BUG_ENTRY_FORMAT(format) \
> + "\t" __BUG_REL(format) "\t# bug_entry::format\n"
> +#else
> +#define __BUG_ENTRY_FORMAT(format)
> +#endif
> +
> +#define __BUG_ENTRY(format, file, line, flags) \
> __BUG_REL("1b") "\t# bug_entry::bug_addr\n" \
> + __BUG_ENTRY_FORMAT(format) \
> __BUG_ENTRY_VERBOSE(file, line) \
> "\t.word " flags "\t# bug_entry::flags\n"
>
> -#define _BUG_FLAGS_ASM(ins, file, line, flags, size, extra) \
> +#define _BUG_FLAGS_ASM(ins, format, file, line, flags, size, extra) \
> "1:\t" ins "\n" \
> ".pushsection __bug_table,\"aw\"\n\t" \
> ANNOTATE_DATA_SPECIAL \
> "2:\n\t" \
> - __BUG_ENTRY(file, line, flags) \
> + __BUG_ENTRY(format, file, line, flags) \
> "\t.org 2b + " size "\n" \
> ".popsection\n" \
> extra
>
> #define _BUG_FLAGS(cond_str, ins, flags, extra) \
> do { \
> - asm_inline volatile(_BUG_FLAGS_ASM(ins, "%c0", \
> - "%c1", "%c2", "%c3", extra) \
> - : : "i" (WARN_CONDITION_STR(cond_str) __FILE__), \
> - "i" (__LINE__), \
> - "i" (flags), \
> - "i" (sizeof(struct bug_entry))); \
> + asm_inline volatile(_BUG_FLAGS_ASM(ins, "%c[fmt]", "%c[file]", \
> + "%c[line]", "%c[fl]", \
> + "%c[size]", extra) \
> + : : [fmt] "i" (NULL), \
This doesn't work right with KASLR on -- and I hadn't noticed because
most of my machines have nokaslr because of debugability :/
When we relocate the kernel, everything shifts by kaslr_offset(), and
that works just fine when both the __bug_table and the target string is
shifted, because then the relative position is the same and so the
relocation keeps working.
However, when the target is the absolute value 0, this breaks, because 0
isn't shifted by kaslr_offset() but the __bug_table itself is.
So the relative entry:
.long 0 - .
and its inverse:
format = (const char *)&bug->format_disp + bug->format_disp;
then end up at kaslr_offset() and things are sad.
The relative entry has a SHN_UNDEF relocation, which is ignored by the
relocs tool.
How is this supposed to be fixed?
> + [file] "i" (WARN_CONDITION_STR(cond_str) __FILE__), \
> + [line] "i" (__LINE__), \
> + [fl] "i" (flags), \
> + [size] "i" (sizeof(struct bug_entry))); \
> } while (0)
>
> #define ARCH_WARN_ASM(file, line, flags, size) \
> - _BUG_FLAGS_ASM(ASM_UD2, file, line, flags, size, "")
> + _BUG_FLAGS_ASM(ASM_UD2, "NULL", file, line, flags, size, "")
>
> #else
>
>
>
next prev parent reply other threads:[~2025-11-25 11:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 11:46 [PATCH v2 00/12] x86: WARN() hackery Peter Zijlstra
2025-11-10 11:46 ` [PATCH v2 01/12] x86: Rework __bug_table helpers Peter Zijlstra
2025-11-10 11:46 ` [PATCH v2 02/12] bug: Add BUG_FORMAT infrastructure Peter Zijlstra
2025-11-10 11:46 ` [PATCH v2 03/12] bug: Clean up CONFIG_GENERIC_BUG_RELATIVE_POINTERS Peter Zijlstra
2025-11-10 11:46 ` [PATCH v2 04/12] bug: Add BUG_FORMAT_ARGS infrastructure Peter Zijlstra
2025-11-10 11:46 ` [PATCH v2 05/12] bug: Add report_bug_entry() Peter Zijlstra
2025-11-10 11:46 ` [PATCH v2 06/12] bug: Implement WARN_ON() using __WARN_FLAGS() Peter Zijlstra
2025-11-10 11:46 ` [PATCH v2 07/12] bug: Allow architectures to provide __WARN_printf() Peter Zijlstra
2025-11-10 11:46 ` [PATCH v2 08/12] x86/bug: Add BUG_FORMAT basics Peter Zijlstra
2025-11-25 11:17 ` Peter Zijlstra [this message]
2025-11-25 12:33 ` Peter Zijlstra
2025-11-25 15:17 ` Peter Zijlstra
2025-11-25 16:27 ` Linus Torvalds
2025-11-26 9:54 ` Peter Zijlstra
2025-11-26 10:56 ` Peter Zijlstra
2025-11-10 11:46 ` [PATCH v2 09/12] x86/bug: Use BUG_FORMAT for DEBUG_BUGVERBOSE_DETAILED Peter Zijlstra
2025-11-10 11:46 ` [PATCH v2 10/12] x86_64/bug: Implement __WARN_printf() Peter Zijlstra
2025-11-11 9:54 ` Peter Zijlstra
2025-11-10 11:46 ` [PATCH v2 11/12] x86/bug: Implement WARN_ONCE() Peter Zijlstra
2025-11-10 11:46 ` [PATCH v2 12/12] x86_64/bug: Inline the UD1 Peter Zijlstra
2025-11-10 16:18 ` [PATCH v2 00/12] x86: WARN() hackery Linus Torvalds
2025-11-10 22:20 ` Peter Zijlstra
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=20251125111750.GS4067720@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acarmina@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=mark.rutland@arm.com \
--cc=torvalds@linuxfoundation.org \
--cc=x86@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.