All of lore.kernel.org
 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 <a.p.zijlstra@chello.nl>,
	Josh Poimboeuf <jpoimboe@redhat.com>
Subject: [GIT PULL] objtool fixes
Date: Sat, 7 Feb 2026 10:58:40 +0100	[thread overview]
Message-ID: <aYcM0KVbWAbrgiY3@gmail.com> (raw)

Linus,

Please pull the latest objtool/urgent Git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git objtool-urgent-2026-02-07

for you to fetch changes up to f495054bd12e2abe5068e243bdf344b704c303c6:

Misc objtool fixes:

 - Bump up the Clang minimum version requirements
   for livepatch builds, due to Clang assembler
   section handling bugs causing silent
   miscompilations.

 - Strip livepatching symbol artifacts from
   non-livepatch modules.

 - Fix livepatch build warnings when certain
   Clang LTO options are enabled.

 - Fix livepatch build error when
   CONFIG_MEM_ALLOC_PROFILING_DEBUG=y.

 Thanks,

	Ingo

------------------>
Josh Poimboeuf (3):
      livepatch/klp-build: Require Clang assembler >= 20
      objtool/klp: Fix symbol correlation for orphaned local symbols
      objtool/klp: Fix unexported static call key access for manually built livepatch modules

Petr Pavlu (2):
      livepatch: Fix having __klp_objects relics in non-livepatch modules
      livepatch: Free klp_{object,func}_ext data after initialization


 include/linux/livepatch.h           |  3 +++
 kernel/livepatch/core.c             | 19 +++++++++++++++++
 scripts/livepatch/init.c            | 20 ++++++++----------
 scripts/livepatch/klp-build         |  4 ++++
 scripts/module.lds.S                |  9 ++------
 tools/objtool/check.c               |  4 ++--
 tools/objtool/include/objtool/klp.h | 10 ++++-----
 tools/objtool/klp-diff.c            | 41 +++++++++++++++++++++++++++++++------
 8 files changed, 79 insertions(+), 31 deletions(-)

             reply	other threads:[~2026-02-07  9:58 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07  9:58 Ingo Molnar [this message]
2026-02-07 17:44 ` [GIT PULL] objtool fixes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-03-22  8:11 Ingo Molnar
2026-03-22 18:04 ` pr-tracker-bot
2026-03-15  3:13 Ingo Molnar
2026-03-15 18:47 ` pr-tracker-bot
2026-02-01  8:46 Ingo Molnar
2026-02-01 19:46 ` pr-tracker-bot
2026-01-24  9:23 Ingo Molnar
2026-01-24 18:00 ` pr-tracker-bot
2026-01-18  9:44 Ingo Molnar
2026-01-19 13:54 ` pr-tracker-bot
2025-12-06 11:37 Ingo Molnar
2025-12-06 20:43 ` pr-tracker-bot
2025-04-10 21:03 Ingo Molnar
2025-04-10 22:52 ` pr-tracker-bot
2025-04-01 19:57 Ingo Molnar
2025-04-02 17:48 ` pr-tracker-bot
2025-04-02 17:58 ` Linus Torvalds
2025-04-02 20:30   ` Ingo Molnar
2025-04-03  8:31   ` Josh Poimboeuf
2025-04-03 14:52     ` Ingo Molnar
2025-04-03 15:23       ` Josh Poimboeuf
2025-04-03 15:33         ` Ingo Molnar
2025-04-03 15:43         ` Josh Poimboeuf
2025-04-03 16:06           ` Linus Torvalds
2025-04-03 18:24             ` Josh Poimboeuf
2025-04-03 19:12               ` Linus Torvalds
2025-04-03 19:42                 ` Josh Poimboeuf
2025-04-03 15:58       ` Linus Torvalds
2025-04-03 15:39     ` Linus Torvalds
2025-02-28 19:08 Ingo Molnar
2025-03-01  1:41 ` pr-tracker-bot
2021-06-24  6:54 Ingo Molnar
2021-06-24 16:34 ` pr-tracker-bot
2021-06-12 12:37 Ingo Molnar
2021-06-12 19:09 ` pr-tracker-bot
2021-05-15  7:46 Ingo Molnar
2021-05-15 17:55 ` pr-tracker-bot
2020-04-25  9:04 Ingo Molnar
2020-04-25 19:30 ` pr-tracker-bot
2018-11-30  6:18 Ingo Molnar
2018-11-30 21:00 ` pr-tracker-bot
2017-11-26 12:34 Ingo Molnar
2017-03-01 22:01 Ingo Molnar
2017-02-28  7:53 Ingo Molnar
2017-03-01  1:55 ` Linus Torvalds
2017-03-01  6:05   ` Josh Poimboeuf
2016-04-23 11:10 Ingo Molnar

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=aYcM0KVbWAbrgiY3@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.