From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] objtool changes for v6.7
Date: Sat, 28 Oct 2023 13:36:01 +0200 [thread overview]
Message-ID: <ZTzyIWSElIo0KZzD@gmail.com> (raw)
Linus,
Please pull the latest objtool tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git objtool-core-2023-10-28
# HEAD: 60fd39af33d3f63c4c94bd06784ebdf0d883f5c9 scripts/faddr2line: Skip over mapping symbols in output from readelf
Misc fixes and cleanups:
- Fix potential MAX_NAME_LEN limit related build failures
- Fix scripts/faddr2line symbol filtering bug
- Fix scripts/faddr2line on LLVM=1
- Fix scripts/faddr2line to accept readelf output with mapping symbols
- Minor cleanups
Thanks,
Ingo
------------------>
Aaron Plattner (2):
objtool: Propagate early errors
objtool: Remove max symbol name length limitation
Colin Ian King (1):
x86/unwind/orc: Remove redundant initialization of 'mid' pointer in __orc_find()
Fangrui Song (1):
x86/speculation, objtool: Use absolute relocations for annotations
Ruan Jinjie (1):
objtool: Use 'the fallthrough' pseudo-keyword
Will Deacon (3):
scripts/faddr2line: Don't filter out non-function symbols from readelf
scripts/faddr2line: Use LLVM addr2line and readelf if LLVM=1
scripts/faddr2line: Skip over mapping symbols in output from readelf
arch/x86/include/asm/alternative.h | 4 ++--
arch/x86/include/asm/nospec-branch.h | 4 ++--
arch/x86/kernel/unwind_orc.c | 2 +-
include/linux/objtool.h | 10 +++++-----
scripts/faddr2line | 24 +++++++++++++++++++++---
tools/objtool/arch/x86/decode.c | 6 +++---
tools/objtool/elf.c | 14 ++++++--------
tools/objtool/objtool.c | 4 +---
8 files changed, 41 insertions(+), 27 deletions(-)
next reply other threads:[~2023-10-28 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 11:36 Ingo Molnar [this message]
2023-10-30 23:50 ` [GIT PULL] objtool changes for v6.7 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=ZTzyIWSElIo0KZzD@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox