From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] objtool/urgent for 5.18
Date: Sun, 1 May 2022 13:44:50 +0200 [thread overview]
Message-ID: <Ym5ysk8Eo4p+0YnU@zn.tnic> (raw)
Hi Linus,
please pull a couple of urgent objtool fixes for 5.18.
Thx.
---
The following changes since commit b2d229d4ddb17db541098b83524d901257e93845:
Linux 5.18-rc3 (2022-04-17 13:57:31 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/objtool_urgent_for_v5.18_rc5
for you to fetch changes up to 4abff6d48dbcea8200c7ea35ba70c242d128ebf3:
objtool: Fix code relocs vs weak symbols (2022-04-22 12:13:55 +0200)
----------------------------------------------------------------
- A bunch of objtool fixes to improve unwinding, sibling call detection,
fallthrough detection and relocation handling of weak symbols when the
toolchain strips section symbols
----------------------------------------------------------------
Josh Poimboeuf (4):
x86/uaccess: Don't jump between functions
objtool: Don't set 'jump_dest' for sibling calls
objtool: Fix sibling call detection in alternatives
objtool: Fix function fallthrough detection for vmlinux
Peter Zijlstra (2):
objtool: Fix type of reloc::addend
objtool: Fix code relocs vs weak symbols
arch/x86/lib/copy_user_64.S | 87 +++++++++------
tools/objtool/check.c | 81 +++++++-------
tools/objtool/elf.c | 189 ++++++++++++++++++++++++++++----
tools/objtool/include/objtool/elf.h | 4 +-
tools/objtool/include/objtool/objtool.h | 2 +-
tools/objtool/objtool.c | 1 -
6 files changed, 265 insertions(+), 99 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2022-05-01 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 11:44 Borislav Petkov [this message]
2022-05-01 17:09 ` 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=Ym5ysk8Eo4p+0YnU@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®