From: patchwork-bot+netdevbpf@kernel.org
To: Saket Kumar Bhaskar <skb99@linux.ibm.com>
Cc: bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, ast@kernel.org,
hbathini@linux.ibm.com, andrii@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, mykolal@fb.com, shuah@kernel.org
Subject: Re: [PATCH] selftests/bpf: Fix fill_link_info selftest on powerpc
Date: Mon, 09 Dec 2024 22:00:30 +0000 [thread overview]
Message-ID: <173378163026.254913.9571999335210274445.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241209065720.234344-1-skb99@linux.ibm.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 9 Dec 2024 12:27:20 +0530 you wrote:
> With CONFIG_KPROBES_ON_FTRACE enabled on powerpc, ftrace_location_range
> returns ftrace location for bpf_fentry_test1 at offset of 4 bytes from
> function entry. This is because branch to _mcount function is at offset
> of 4 bytes in function profile sequence.
>
> To fix this, add entry_offset of 4 bytes while verifying the address for
> kprobe entry address of bpf_fentry_test1 in verify_perf_link_info in
> selftest, when CONFIG_KPROBES_ON_FTRACE is enabled.
>
> [...]
Here is the summary with links:
- selftests/bpf: Fix fill_link_info selftest on powerpc
https://git.kernel.org/bpf/bpf-next/c/4d33dc1bc31d
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:[~2024-12-09 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 6:57 [PATCH] selftests/bpf: Fix fill_link_info selftest on powerpc Saket Kumar Bhaskar
2024-12-09 22:00 ` 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=173378163026.254913.9571999335210274445.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=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hbathini@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=skb99@linux.ibm.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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