From: patchwork-bot+netdevbpf@kernel.org
To: Philo Lu <lulie@linux.alibaba.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, mykolal@fb.com,
shuah@kernel.org, xuanzhuo@linux.alibaba.com
Subject: Re: [PATCH bpf-next v1 0/3] bpf: allow bpf_for_each_map_elem() helper with different input maps
Date: Fri, 05 Apr 2024 17:40:29 +0000 [thread overview]
Message-ID: <171233882923.27871.7584547552854184481.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240405025536.18113-1-lulie@linux.alibaba.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 5 Apr 2024 10:55:33 +0800 you wrote:
> Currently, taking different maps within a single bpf_for_each_map_elem
> call is not allowed. For example the following codes cannot pass the
> verifier (with error "tail_call abusing map_ptr"):
> ```
> static void test_by_pid(int pid)
> {
> if (pid <= 100)
> bpf_for_each_map_elem(&map1, map_elem_cb, NULL, 0);
> else
> bpf_for_each_map_elem(&map2, map_elem_cb, NULL, 0);
> }
> ```
>
> [...]
Here is the summary with links:
- [bpf-next,v1,1/3] bpf: store both map ptr and state in bpf_insn_aux_data
https://git.kernel.org/bpf/bpf-next/c/0a525621b7e5
- [bpf-next,v1,2/3] bpf: allow invoking bpf_for_each_map_elem with different maps
https://git.kernel.org/bpf/bpf-next/c/9d482da9e17a
- [bpf-next,v1,3/3] selftests/bpf: add test for bpf_for_each_map_elem() with different maps
https://git.kernel.org/bpf/bpf-next/c/fecb1597cc11
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-04-05 17:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 2:55 [PATCH bpf-next v1 0/3] bpf: allow bpf_for_each_map_elem() helper with different input maps Philo Lu
2024-04-05 2:55 ` [PATCH bpf-next v1 1/3] bpf: store both map ptr and state in bpf_insn_aux_data Philo Lu
2024-04-05 16:36 ` Yonghong Song
2024-04-05 2:55 ` [PATCH bpf-next v1 2/3] bpf: allow invoking bpf_for_each_map_elem with different maps Philo Lu
2024-04-05 16:37 ` Yonghong Song
2024-04-05 2:55 ` [PATCH bpf-next v1 3/3] selftests/bpf: add test for bpf_for_each_map_elem() " Philo Lu
2024-04-05 16:39 ` Yonghong Song
2024-04-05 17:35 ` Andrii Nakryiko
2024-04-05 17:41 ` Alexei Starovoitov
2024-04-05 17:52 ` Andrii Nakryiko
2024-04-05 17:40 ` 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=171233882923.27871.7584547552854184481.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=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=lulie@linux.alibaba.com \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yonghong.song@linux.dev \
/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