From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
sdf@google.com, haoluo@google.com, mhiramat@kernel.org,
peterz@infradead.org, m@lambda.lt
Subject: Re: [PATCHv5 bpf-next 0/6] bpf: Fixes for CONFIG_X86_KERNEL_IBT
Date: Tue, 27 Sep 2022 03:40:16 +0000 [thread overview]
Message-ID: <166425001686.15909.4135024467918166776.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220926153340.1621984-1-jolsa@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 26 Sep 2022 17:33:34 +0200 you wrote:
> hi,
> Martynas reported bpf_get_func_ip returning +4 address when
> CONFIG_X86_KERNEL_IBT option is enabled and I found there are
> some failing bpf tests when this option is enabled.
>
> The CONFIG_X86_KERNEL_IBT option adds endbr instruction at the
> function entry, so the idea is to 'fix' entry ip for kprobe_multi
> and trampoline probes, because they are placed on the function
> entry.
>
> [...]
Here is the summary with links:
- [PATCHv5,bpf-next,1/6] kprobes: Add new KPROBE_FLAG_ON_FUNC_ENTRY kprobe flag
https://git.kernel.org/bpf/bpf-next/c/bf7a87f1075f
- [PATCHv5,bpf-next,2/6] ftrace: Keep the resolved addr in kallsyms_callback
https://git.kernel.org/bpf/bpf-next/c/9d68c19c57d6
- [PATCHv5,bpf-next,3/6] bpf: Use given function address for trampoline ip arg
https://git.kernel.org/bpf/bpf-next/c/4d854f4f31ec
- [PATCHv5,bpf-next,4/6] bpf: Adjust kprobe_multi entry_ip for CONFIG_X86_KERNEL_IBT
https://git.kernel.org/bpf/bpf-next/c/c09eb2e578eb
- [PATCHv5,bpf-next,5/6] bpf: Return value in kprobe get_func_ip only for entry address
https://git.kernel.org/bpf/bpf-next/c/0e253f7e558a
- [PATCHv5,bpf-next,6/6] selftests/bpf: Fix get_func_ip offset test for CONFIG_X86_KERNEL_IBT
https://git.kernel.org/bpf/bpf-next/c/738c345b74b8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-09-27 3:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 15:33 [PATCHv5 bpf-next 0/6] bpf: Fixes for CONFIG_X86_KERNEL_IBT Jiri Olsa
2022-09-26 15:33 ` [PATCHv5 bpf-next 1/6] kprobes: Add new KPROBE_FLAG_ON_FUNC_ENTRY kprobe flag Jiri Olsa
2022-09-26 15:33 ` [PATCHv5 bpf-next 2/6] ftrace: Keep the resolved addr in kallsyms_callback Jiri Olsa
2022-09-26 15:33 ` [PATCHv5 bpf-next 3/6] bpf: Use given function address for trampoline ip arg Jiri Olsa
2022-09-26 15:33 ` [PATCHv5 bpf-next 4/6] bpf: Adjust kprobe_multi entry_ip for CONFIG_X86_KERNEL_IBT Jiri Olsa
2022-09-26 15:33 ` [PATCHv5 bpf-next 5/6] bpf: Return value in kprobe get_func_ip only for entry address Jiri Olsa
2022-09-26 15:33 ` [PATCHv5 bpf-next 6/6] selftests/bpf: Fix get_func_ip offset test for CONFIG_X86_KERNEL_IBT Jiri Olsa
2022-09-26 18:28 ` [PATCHv5 bpf-next 0/6] bpf: Fixes " Peter Zijlstra
2022-09-27 3:40 ` patchwork-bot+netdevbpf [this message]
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=166425001686.15909.4135024467918166776.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=m@lambda.lt \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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.