From: patchwork-bot+netdevbpf@kernel.org
To: Runqing Yang <rainkin1993@gmail.com>
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@kernel.org
Subject: Re: [bpf-next] libbpf: Fix a bug that checking bpf_probe_read_kernel API fails in old kernels
Date: Mon, 11 Apr 2022 03:20:12 +0000 [thread overview]
Message-ID: <164964721253.11578.7623906648168365938.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220409144928.27499-1-rainkin1993@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sat, 9 Apr 2022 22:49:28 +0800 you wrote:
> Background:
> Libbpf automatically replaces calls to BPF bpf_probe_read_{kernel,user}
> [_str]() helpers with bpf_probe_read[_str](), if libbpf detects that
> kernel doesn't support new APIs. Specifically, libbpf invokes the
> probe_kern_probe_read_kernel function to load a small eBPF program into
> the kernel in which bpf_probe_read_kernel API is invoked and lets the
> kernel checks whether the new API is valid. If the loading fails, libbpf
> considers the new API invalid and replaces it with the old API.
>
> [...]
Here is the summary with links:
- [bpf-next] libbpf: Fix a bug that checking bpf_probe_read_kernel API fails in old kernels
https://git.kernel.org/bpf/bpf-next/c/d252a4a499a0
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-04-11 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 14:49 [bpf-next] libbpf: Fix a bug that checking bpf_probe_read_kernel API fails in old kernels Runqing Yang
2022-04-11 3: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=164964721253.11578.7623906648168365938.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=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=rainkin1993@gmail.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.