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, ravi.bangoria@amd.com,
linux-perf-users@vger.kernel.org, acme@kernel.org
Subject: Re: [PATCH bpf-next] libbpf: only reset sec_def handler when necessary
Date: Sun, 09 Jul 2023 01:40:20 +0000 [thread overview]
Message-ID: <168886682064.2231.10209973851568634649.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230707231156.1711948-1-andrii@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 7 Jul 2023 16:11:56 -0700 you wrote:
> Don't reset recorded sec_def handler unconditionally on
> bpf_program__set_type(). There are two situations where this is wrong.
>
> First, if the program type didn't actually change. In that case original
> SEC handler should work just fine.
>
> Second, catch-all custom SEC handler is supposed to work with any BPF
> program type and SEC() annotation, so it also doesn't make sense to
> reset that.
>
> [...]
Here is the summary with links:
- [bpf-next] libbpf: only reset sec_def handler when necessary
https://git.kernel.org/bpf/bpf-next/c/c628747cc880
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-07-09 1:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 23:11 [PATCH bpf-next] libbpf: only reset sec_def handler when necessary Andrii Nakryiko
2023-07-08 0:15 ` Stanislav Fomichev
2023-07-09 1:40 ` patchwork-bot+netdevbpf [this message]
2023-07-12 8:40 ` Gal Pressman
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=168886682064.2231.10209973851568634649.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-perf-users@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=ravi.bangoria@amd.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.