From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, linux-perf-users@vger.kernel.org,
kernel-team@meta.com, acme@redhat.com, lmb@isovalent.com
Subject: Re: [PATCH bpf] libbpf: handle unsupported mmap-based /sys/kernel/btf/vmlinux correctly
Date: Fri, 06 Jun 2025 21:20:29 +0000 [thread overview]
Message-ID: <174924482950.3997280.17986283354831226329.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250606202134.2738910-1-andrii@kernel.org>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 6 Jun 2025 13:21:34 -0700 you wrote:
> libbpf_err_ptr() helpers are meant to return NULL and set errno, if
> there is an error. But btf_parse_raw_mmap() is meant to be used
> internally and is expected to return ERR_PTR() values. Because of this
> mismatch, when libbpf tries to mmap /sys/kernel/btf/vmlinux, we don't
> detect the error correctly with IS_ERR() check, and never fallback to
> old non-mmap-based way of loading vmlinux BTF.
>
> [...]
Here is the summary with links:
- [bpf] libbpf: handle unsupported mmap-based /sys/kernel/btf/vmlinux correctly
https://git.kernel.org/bpf/bpf/c/02670deede22
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:[~2025-06-06 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 20:21 [PATCH bpf] libbpf: handle unsupported mmap-based /sys/kernel/btf/vmlinux correctly Andrii Nakryiko
2025-06-06 21:20 ` 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=174924482950.3997280.17986283354831226329.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@redhat.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=lmb@isovalent.com \
--cc=martin.lau@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 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.