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, kernel-team@meta.com
Subject: Re: [PATCH bpf-next] libbpf: fix return value for PERF_EVENT __arg_ctx type fix up check
Date: Tue, 06 Feb 2024 04:20:26 +0000 [thread overview]
Message-ID: <170719322643.4467.580963372525626194.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240206002243.1439450-1-andrii@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 5 Feb 2024 16:22:43 -0800 you wrote:
> If PERF_EVENT program has __arg_ctx argument with matching
> architecture-specific pt_regs/user_pt_regs/user_regs_struct pointer
> type, libbpf should still perform type rewrite for old kernels, but not
> emit the warning. Fix copy/paste from kernel code where 0 is meant to
> signify "no error" condition. For libbpf we need to return "true" to
> proceed with type rewrite (which for PERF_EVENT program will be
> a canonical `struct bpf_perf_event_data *` type).
>
> [...]
Here is the summary with links:
- [bpf-next] libbpf: fix return value for PERF_EVENT __arg_ctx type fix up check
https://git.kernel.org/bpf/bpf-next/c/d7bc416aa5cc
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-02-06 4:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 0:22 [PATCH bpf-next] libbpf: fix return value for PERF_EVENT __arg_ctx type fix up check Andrii Nakryiko
2024-02-06 4: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=170719322643.4467.580963372525626194.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@meta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox