From: Joe Lawrence <joe.lawrence@redhat.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, live-patching@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>, Song Liu <song@kernel.org>,
Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH v2] objtool/klp: Fix checksums for constant pool references
Date: Thu, 10 Sep 2026 17:05:06 -0400 [thread overview]
Message-ID: <be81497f-1b88-4337-b577-0f3a2b7828b0@redhat.com> (raw)
In-Reply-To: <f3a9e74ceebc6475ce94bcfe985401140857814a.1787939301.git.jpoimboe@kernel.org>
On 8/28/26 1:48 PM, Josh Poimboeuf wrote:
> Adding a line of code to __link_shadow_page() with a literal string
> causes a false positive changed function with GCC:
>
> arch/x86/kvm/kvm.ko.o: changed function: kvm_tdp_mmu_map_private_pfn
>
> While the patch only touched __link_shadow_page(), the string addition
> triggered a rename of .LC64 -> .LC65 in kvm_tdp_mmu_map_private_pfn()
> even though the underlying referenced constant data didn't change.
>
> So for .LC* symbols, the suffix is arbitrary but the data isn't. Add
> the underlying data to the checksum calculation rather than the symbol
> name.
>
> Clang also uses .LC* symbols, but also uses anonymous data. Both
> compilers put this data in .rodata.cst<num> sections.
>
> Fixes: 0d83da43b1e1 ("objtool/klp: Add --checksum option to generate per-function checksums")
> Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
> ---
> tools/objtool/klp-checksum.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/tools/objtool/klp-checksum.c b/tools/objtool/klp-checksum.c
> index b8e47f28997e9..ebe25f9c5260a 100644
> --- a/tools/objtool/klp-checksum.c
> +++ b/tools/objtool/klp-checksum.c
> @@ -54,6 +54,19 @@ static int checksum_debug_init(struct objtool_file *file)
> return 0;
> }
>
> +/*
> + * Detect a reference to anonymous constant pool data which the compiler places
> + * in .rodata.cst<num> and which either has an .LC<num> symbol associated with
> + * it or (with Clang) no symbol at all. These are typically initializers for
> + * local function stack data, so they're considered part of the function rather
> + * than data per se.
> + */
> +static bool is_anonymous_const_data(struct symbol *sym)
> +{
> + return strstarts(sym->sec->name, ".rodata.cst") &&
> + (is_sec_sym(sym) || strstarts(sym->name, ".LC"));
> +}
> +
> static void checksum_update_insn(struct objtool_file *file, struct symbol *func,
> struct instruction *insn)
> {
> @@ -129,6 +142,14 @@ static void checksum_update_insn(struct objtool_file *file, struct symbol *func,
> goto alts;
> }
>
> + if (is_anonymous_const_data(sym)) {
> + void *cst;
> +
> + cst = sym->sec->data->d_buf + sym->offset + offset;
> + __checksum_update_insn(func, insn, cst, sym->sec->sh.sh_entsize);
> + goto alts;
> + }
> +
> if (is_sec_sym(sym)) {
> sym = find_symbol_containing(reloc->sym->sec, offset);
> if (!sym)
Acked-by: Joe Lawrence <joe.lawrence@redhat.com>
--
Joe
prev parent reply other threads:[~2026-09-10 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 17:48 [PATCH v2] objtool/klp: Fix checksums for constant pool references Josh Poimboeuf
2026-08-28 17:59 ` sashiko-bot
2026-08-28 18:21 ` Josh Poimboeuf
2026-09-10 21:05 ` Joe Lawrence [this message]
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=be81497f-1b88-4337-b577-0f3a2b7828b0@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=song@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox