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.11-rc5
Date: Sun, 24 Jan 2021 13:15:39 +0100 [thread overview]
Message-ID: <20210124121539.GD2493@zn.tnic> (raw)
Hi Linus,
please pull three urgent objtool fixes resulting from recent toolchain
changes.
Thx.
---
The following changes since commit 7c53f6b671f4aba70ff15e1b05148b10d58c2837:
Linux 5.11-rc3 (2021-01-10 14:34:50 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/objtool_urgent_for_v5.11_rc5
for you to fetch changes up to 1d489151e9f9d1647110277ff77282fe4d96d09b:
objtool: Don't fail on missing symbol table (2021-01-21 15:49:58 -0600)
----------------------------------------------------------------
- Adjust objtool to handle a recent binutils change to not generate unused
symbols anymore.
- Revert the fail-the-build-on-fatal-errors objtool strategy for now due to the
ever-increasing matrix of supported toolchains/plugins and them causing too
many such fatal errors currently.
- Do not add empty symbols to objdump's rbtree to accommodate clang removing
section symbols.
----------------------------------------------------------------
Josh Poimboeuf (3):
objtool: Don't add empty symbols to the rbtree
objtool: Don't fail the kernel build on fatal errors
objtool: Don't fail on missing symbol table
tools/objtool/check.c | 14 +++++---------
tools/objtool/elf.c | 14 ++++++++++++--
2 files changed, 17 insertions(+), 11 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2021-01-24 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 12:15 Borislav Petkov [this message]
2021-01-24 18:34 ` 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=20210124121539.GD2493@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®