From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next v2] selftests/bpf: Ignore .llvm.<hash> suffix in kallsyms_find()
Date: Tue, 04 Jun 2024 20:10:28 +0000 [thread overview]
Message-ID: <171753182854.20801.387571766862079900.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240604180034.1356016-1-yonghong.song@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 4 Jun 2024 11:00:34 -0700 you wrote:
> I hit the following failure when running selftests with
> internal backported upstream kernel:
> test_ksyms:PASS:kallsyms_fopen 0 nsec
> test_ksyms:FAIL:ksym_find symbol 'bpf_link_fops' not found
> #123 ksyms:FAIL
>
> In /proc/kallsyms, we have
> $ cat /proc/kallsyms | grep bpf_link_fops
> ffffffff829f0cb0 d bpf_link_fops.llvm.12608678492448798416
> The CONFIG_LTO_CLANG_THIN is enabled in the kernel which is responsible
> for bpf_link_fops.llvm.12608678492448798416 symbol name.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] selftests/bpf: Ignore .llvm.<hash> suffix in kallsyms_find()
https://git.kernel.org/bpf/bpf-next/c/898ac74c5b5f
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-06-04 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 18:00 [PATCH bpf-next v2] selftests/bpf: Ignore .llvm.<hash> suffix in kallsyms_find() Yonghong Song
2024-06-04 20:10 ` 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=171753182854.20801.387571766862079900.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=kernel-team@fb.com \
--cc=martin.lau@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