From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] objtool/urgent for 5.8
Date: Sun, 28 Jun 2020 16:12:45 +0200 [thread overview]
Message-ID: <20200628141245.GB18884@zn.tnic> (raw)
Hi Linus,
please pull three fixes from peterz suppressing KCOV instrumentation in
noinstr sections.
Thx.
---
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/objtool_urgent_for_5.8_rc3
for you to fetch changes up to 0f1441b44e823a74f3f3780902a113e07c73fbf6:
objtool: Fix noinstr vs KCOV (2020-06-18 17:36:33 +0200)
----------------------------------------------------------------
Peter Zijlstra says:
Address KCOV vs noinstr. There is no function attribute to selectively
suppress KCOV instrumentation, instead teach objtool to NOP out the
calls in noinstr functions.
This cures a bunch of KCOV crashes (as used by syzcaller).
----------------------------------------------------------------
Peter Zijlstra (3):
objtool: Clean up elf_write() condition
objtool: Provide elf_write_{insn,reloc}()
objtool: Fix noinstr vs KCOV
arch/x86/Kconfig | 2 +-
tools/objtool/arch.h | 2 ++
tools/objtool/arch/x86/decode.c | 18 +++++++++++
tools/objtool/arch/x86/include/arch_elf.h | 6 ++++
tools/objtool/check.c | 23 +++++++++++++-
tools/objtool/elf.c | 53 +++++++++++++++++++++++++++++--
tools/objtool/elf.h | 12 +++++--
tools/objtool/orc_gen.c | 2 +-
8 files changed, 109 insertions(+), 9 deletions(-)
create mode 100644 tools/objtool/arch/x86/include/arch_elf.h
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2020-06-28 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 14:12 Borislav Petkov [this message]
2020-06-28 18:45 ` 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=20200628141245.GB18884@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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®