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 v5.15-rc5
Date: Sun, 10 Oct 2021 11:05:13 +0200 [thread overview]
Message-ID: <YWKsyUevMivmrxdZ@zn.tnic> (raw)
Hi Linus,
please pull three urgent objtool fixes for v5.15-rc5.
Thx.
---
The following changes since commit 9e1ff307c779ce1f0f810c7ecce3d95bbae40896:
Linux 5.15-rc4 (2021-10-03 14:08:47 -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.15_rc5
for you to fetch changes up to fe255fe6ad97685e5a4be0d871f43288dbc10ad6:
objtool: Remove redundant 'len' field from struct section (2021-10-05 12:03:21 -0700)
----------------------------------------------------------------
- Remove an extra section.len member in favour of section.sh_size
- Align .altinstructions section creation with the kernel's by creating
them with entry size of 0
- Fix objtool to convert a reloc symbol to a section offset and not to
not warn about not knowing how
----------------------------------------------------------------
Joe Lawrence (2):
objtool: Make .altinstructions section entry size consistent
objtool: Remove redundant 'len' field from struct section
Josh Poimboeuf (1):
objtool: Remove reloc symbol type checks in get_alt_entry()
tools/objtool/arch/x86/decode.c | 2 +-
tools/objtool/check.c | 16 +++++++--------
tools/objtool/elf.c | 14 ++++++-------
tools/objtool/include/objtool/elf.h | 1 -
tools/objtool/orc_gen.c | 2 +-
tools/objtool/special.c | 40 +++++++++----------------------------
6 files changed, 25 insertions(+), 50 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2021-10-10 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 9:05 Borislav Petkov [this message]
2021-10-10 17:17 ` 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=YWKsyUevMivmrxdZ@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®