From: Josh Poimboeuf <jpoimboe@kernel.org>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org, live-patching@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Joe Lawrence <joe.lawrence@redhat.com>,
Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
Song Liu <song@kernel.org>
Subject: [PATCH v2 0/7] objtool/klp: sympos/module/alternative/etc fixes
Date: Wed, 5 Aug 2026 07:29:37 -0700 [thread overview]
Message-ID: <cover.1785939903.git.jpoimboe@kernel.org> (raw)
v2:
- rebased on tip/master (first 6 patches were merged)
- dropped original patches 7-8 (will post followup)
- added .klp.symid fix
v1: https://lore.kernel.org/cover.1785727106.git.jpoimboe@kernel.org
This consolidates fixes for the klp-build issues reported by Joe over
the last several weeks, plus some more things I found while
testing/reviewing.
Fun stuff like symbol resolution, module dependencies, alternatives.
Joe Lawrence (1):
objtool/klp: Allow new references to module exports
Josh Poimboeuf (6):
objtool/klp: Fix vmlinux .klp.symid link error for .no_trim_symbol
symbols
objtool/klp: Fix size of empty special section entries
objtool/klp: Ignore replacement offset of empty x86 alternatives
objtool/klp: Explicitly disallow patching or referencing init
code/data
objtool/klp: Fix cross-module klp relocation section naming
objtool/klp: Don't match local symbols against exports
tools/objtool/arch/x86/special.c | 27 ++++++++++
tools/objtool/include/objtool/klp.h | 10 ++--
tools/objtool/include/objtool/special.h | 7 +++
tools/objtool/klp-diff.c | 65 ++++++++++++++++++++++---
tools/objtool/klp-post-link.c | 53 +++++++++++---------
tools/objtool/klp-symid.c | 1 +
tools/objtool/klp-sympos.c | 10 ++++
7 files changed, 141 insertions(+), 32 deletions(-)
--
2.54.0
next reply other threads:[~2026-08-05 14:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 14:29 Josh Poimboeuf [this message]
2026-08-05 14:29 ` [PATCH v2 1/7] objtool/klp: Fix vmlinux .klp.symid link error for .no_trim_symbol symbols Josh Poimboeuf
2026-08-05 18:30 ` Song Liu
2026-08-05 14:29 ` [PATCH v2 2/7] objtool/klp: Fix size of empty special section entries Josh Poimboeuf
2026-08-05 20:36 ` Song Liu
2026-08-06 5:11 ` Josh Poimboeuf
2026-08-06 20:51 ` Song Liu
2026-08-05 14:29 ` [PATCH v2 3/7] objtool/klp: Ignore replacement offset of empty x86 alternatives Josh Poimboeuf
2026-08-05 20:51 ` Song Liu
2026-08-06 5:14 ` Josh Poimboeuf
2026-08-05 14:29 ` [PATCH v2 4/7] objtool/klp: Explicitly disallow patching or referencing init code/data Josh Poimboeuf
2026-08-05 15:12 ` sashiko-bot
2026-08-06 5:26 ` Josh Poimboeuf
2026-08-05 14:29 ` [PATCH v2 5/7] objtool/klp: Fix cross-module klp relocation section naming Josh Poimboeuf
2026-08-05 22:23 ` Song Liu
2026-08-05 14:29 ` [PATCH v2 6/7] objtool/klp: Don't match local symbols against exports Josh Poimboeuf
2026-08-05 20:59 ` Song Liu
2026-08-05 14:29 ` [PATCH v2 7/7] objtool/klp: Allow new references to module exports Josh Poimboeuf
2026-08-05 22:24 ` Song Liu
2026-08-06 15:57 ` [PATCH v2 0/7] objtool/klp: sympos/module/alternative/etc fixes Joe Lawrence
2026-08-07 1:25 ` Josh Poimboeuf
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=cover.1785939903.git.jpoimboe@kernel.org \
--to=jpoimboe@kernel.org \
--cc=joe.lawrence@redhat.com \
--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