All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: bp@alien8.de, hpa@zytor.com, jpoimboe@redhat.com,
	songliubraving@fb.com, tglx@linutronix.de, rostedt@goodmis.org,
	kasong@redhat.com, daniel@iogearbox.net, ast@kernel.org,
	peterz@infradead.org, linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] bpf: Fix ORC unwinding in non-JIT BPF code
Date: Sat, 6 Jul 2019 22:29:42 +0200	[thread overview]
Message-ID: <20190706202942.GA123403@gmail.com> (raw)
In-Reply-To: <tip-b22cf36c189f31883ad0238a69ccf82aa1f3b16b@git.kernel.org>


* tip-bot for Josh Poimboeuf <tipbot@zytor.com> wrote:

> Commit-ID:  b22cf36c189f31883ad0238a69ccf82aa1f3b16b
> Gitweb:     https://git.kernel.org/tip/b22cf36c189f31883ad0238a69ccf82aa1f3b16b
> Author:     Josh Poimboeuf <jpoimboe@redhat.com>
> AuthorDate: Thu, 27 Jun 2019 20:50:47 -0500
> Committer:  Thomas Gleixner <tglx@linutronix.de>
> CommitDate: Sat, 29 Jun 2019 07:55:14 +0200
> 
> bpf: Fix ORC unwinding in non-JIT BPF code
> 
> Objtool previously ignored ___bpf_prog_run() because it didn't understand
> the jump table.  This resulted in the ORC unwinder not being able to unwind
> through non-JIT BPF code.
> 
> Now that objtool knows how to read jump tables, remove the whitelist and
> annotate the jump table so objtool can recognize it.
> 
> Also add an additional "const" to the jump table definition to clarify that
> the text pointers are constant.  Otherwise GCC sets the section writable
> flag and the assembler spits out warnings.
> 
> Fixes: d15d356887e7 ("perf/x86: Make perf callchains work without CONFIG_FRAME_POINTER")
> Reported-by: Song Liu <songliubraving@fb.com>
> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Acked-by: Alexei Starovoitov <ast@kernel.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Kairui Song <kasong@redhat.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: Daniel Borkmann <daniel@iogearbox.net>
> Link: https://lkml.kernel.org/r/881939122b88f32be4c374d248c09d7527a87e35.1561685471.git.jpoimboe@redhat.com
> 
> ---
>  kernel/bpf/core.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)

Hm, I get this new build warning on x86-64 defconfig-ish kernels plus 
these enabled:

 CONFIG_BPF=y
 CONFIG_BPF_JIT=y

kernel/bpf/core.o: warning: objtool: ___bpf_prog_run()+0x8da: sibling call from callable instruction with modified stack frame

Thanks,

	Ingo

  reply	other threads:[~2019-07-06 20:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28  1:50 [PATCH v4 0/2] x86: bpf unwinder fixes Josh Poimboeuf
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 [this message]
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=20190706202942.GA123403@gmail.com \
    --to=mingo@kernel.org \
    --cc=ast@kernel.org \
    --cc=bp@alien8.de \
    --cc=daniel@iogearbox.net \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@redhat.com \
    --cc=kasong@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=songliubraving@fb.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.