From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@google.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
haoluo@google.com, jolsa@kernel.org
Subject: Re: [PATCH bpf-next v5 0/5] bpf: expose bpf_{g,s}et_retval to more cgroup hooks
Date: Tue, 23 Aug 2022 23:20:17 +0000 [thread overview]
Message-ID: <166129681731.10727.1913185417224376513.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220823222555.523590-1-sdf@google.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 23 Aug 2022 15:25:50 -0700 you wrote:
> Apparently, only a small subset of cgroup hooks actually falls
> back to cgroup_base_func_proto. This leads to unexpected result
> where not all cgroup helpers have bpf_{g,s}et_retval.
>
> It's getting harder and harder to manage which helpers are exported
> to which hooks. We now have the following call chains:
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/5] bpf: Introduce cgroup_{common,current}_func_proto
https://git.kernel.org/bpf/bpf-next/c/dea6a4e17013
- [bpf-next,v5,2/5] bpf: Use cgroup_{common,current}_func_proto in more hooks
https://git.kernel.org/bpf/bpf-next/c/bed89185af0d
- [bpf-next,v5,3/5] bpf: expose bpf_strtol and bpf_strtoul to all program types
https://git.kernel.org/bpf/bpf-next/c/8a67f2de9b1d
- [bpf-next,v5,4/5] bpf: update bpf_{g,s}et_retval documentation
https://git.kernel.org/bpf/bpf-next/c/2172fb8007ea
- [bpf-next,v5,5/5] selftests/bpf: Make sure bpf_{g,s}et_retval is exposed everywhere
https://git.kernel.org/bpf/bpf-next/c/e7215f574079
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-08-23 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 22:25 [PATCH bpf-next v5 0/5] bpf: expose bpf_{g,s}et_retval to more cgroup hooks Stanislav Fomichev
2022-08-23 22:25 ` [PATCH bpf-next v5 1/5] bpf: Introduce cgroup_{common,current}_func_proto Stanislav Fomichev
2022-08-23 22:59 ` Martin KaFai Lau
2022-08-23 22:25 ` [PATCH bpf-next v5 2/5] bpf: Use cgroup_{common,current}_func_proto in more hooks Stanislav Fomichev
2022-08-23 22:25 ` [PATCH bpf-next v5 3/5] bpf: expose bpf_strtol and bpf_strtoul to all program types Stanislav Fomichev
2022-08-23 22:25 ` [PATCH bpf-next v5 4/5] bpf: update bpf_{g,s}et_retval documentation Stanislav Fomichev
2022-08-23 22:25 ` [PATCH bpf-next v5 5/5] selftests/bpf: Make sure bpf_{g,s}et_retval is exposed everywhere Stanislav Fomichev
2022-08-23 23: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=166129681731.10727.1913185417224376513.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox