From: Josh Poimboeuf <jpoimboe@redhat.com>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Song Liu <songliubraving@fb.com>, Kairui Song <kasong@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH v4 0/2] x86: bpf unwinder fixes
Date: Thu, 27 Jun 2019 20:50:45 -0500 [thread overview]
Message-ID: <cover.1561685471.git.jpoimboe@redhat.com> (raw)
Here's the last fix along with its objtool dependency.
For testing I verified that a WARN() in ___bpf_prog_run() now gives a
clean stack trace.
v4:
- Redesigned the jump table detection mechanism. Instead of requiring
the jump table to have a magic name, place it in a special section.
- The other two fixes from v3 have been merged into -tip.
Josh Poimboeuf (2):
objtool: Add support for C jump tables
bpf: Fix ORC unwinding in non-JIT BPF code
include/linux/compiler.h | 5 +++++
kernel/bpf/core.c | 3 +--
tools/objtool/check.c | 27 ++++++++++++++++++++-------
3 files changed, 26 insertions(+), 9 deletions(-)
--
2.20.1
next reply other threads:[~2019-06-28 1:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 1:50 Josh Poimboeuf [this message]
2019-06-28 1:50 ` [PATCH v4 1/2] objtool: Add support for C jump tables Josh Poimboeuf
2019-06-29 5:58 ` [tip:x86/urgent] " tip-bot for Josh Poimboeuf
2019-07-09 12:01 ` [tip:x86/debug] " tip-bot for Josh Poimboeuf
2019-06-28 1:50 ` [PATCH v4 2/2] bpf: Fix ORC unwinding in non-JIT BPF code Josh Poimboeuf
2019-06-28 15:37 ` Alexei Starovoitov
2019-06-29 5:58 ` [tip:x86/urgent] " tip-bot for Josh Poimboeuf
2019-07-06 20:29 ` Ingo Molnar
2019-07-07 1:32 ` Josh Poimboeuf
2019-07-07 5:52 ` Josh Poimboeuf
2019-07-08 22:15 ` Alexei Starovoitov
2019-07-08 22:38 ` Josh Poimboeuf
2019-07-08 22:49 ` Alexei Starovoitov
2019-07-08 22:53 ` Josh Poimboeuf
2019-07-08 23:02 ` Josh Poimboeuf
2019-07-08 23:16 ` Alexei Starovoitov
2019-07-09 17:47 ` Josh Poimboeuf
2019-07-09 18:02 ` Alexei Starovoitov
2019-07-09 19:17 ` Josh Poimboeuf
2019-07-09 19:26 ` Daniel Borkmann
2019-07-09 12:02 ` [tip:x86/debug] " tip-bot for Josh Poimboeuf
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=cover.1561685471.git.jpoimboe@redhat.com \
--to=jpoimboe@redhat.com \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=daniel@iogearbox.net \
--cc=kasong@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--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