From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Yonghong Song <yhs@fb.com>
Cc: Andrii Nakryiko <andriin@fb.com>, bpf <bpf@vger.kernel.org>,
Martin KaFai Lau <kafai@fb.com>,
Networking <netdev@vger.kernel.org>,
Alexei Starovoitov <ast@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH bpf-next v3 10/21] net: bpf: add netlink and ipv6_route bpf_iter targets
Date: Fri, 8 May 2020 12:17:15 -0700 [thread overview]
Message-ID: <CAEf4BzYvwCaG9sTFM-mJXRF-BosuRRe+URZpVUvrke-nXABivA@mail.gmail.com> (raw)
In-Reply-To: <20200507053926.1543403-1-yhs@fb.com>
On Wed, May 6, 2020 at 10:40 PM Yonghong Song <yhs@fb.com> wrote:
>
> This patch added netlink and ipv6_route targets, using
> the same seq_ops (except show() and minor changes for stop())
> for /proc/net/{netlink,ipv6_route}.
>
> The net namespace for these targets are the current net
> namespace at file open stage, similar to
> /proc/net/{netlink,ipv6_route} reference counting
> the net namespace at seq_file open stage.
>
> Since module is not supported for now, ipv6_route is
> supported only if the IPV6 is built-in, i.e., not compiled
> as a module. The restriction can be lifted once module
> is properly supported for bpf_iter.
>
> Signed-off-by: Yonghong Song <yhs@fb.com>
> ---
Looks correct.
Acked-by: Andrii Nakryiko <andriin@fb.com>
> fs/proc/proc_net.c | 19 +++++++++
> include/linux/proc_fs.h | 3 ++
> net/ipv6/ip6_fib.c | 65 +++++++++++++++++++++++++++++-
> net/ipv6/route.c | 37 +++++++++++++++++
> net/netlink/af_netlink.c | 87 +++++++++++++++++++++++++++++++++++++++-
> 5 files changed, 207 insertions(+), 4 deletions(-)
>
[...]
> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
> index 3912aac7854d..25f6d3e619d0 100644
> --- a/net/ipv6/route.c
> +++ b/net/ipv6/route.c
> @@ -6393,6 +6393,30 @@ void __init ip6_route_init_special_entries(void)
> #endif
> }
>
> +#if IS_BUILTIN(CONFIG_IPV6)
> +#if defined(CONFIG_BPF_SYSCALL) && defined(CONFIG_PROC_FS)
> +DEFINE_BPF_ITER_FUNC(ipv6_route, struct bpf_iter_meta *meta, struct fib6_info *rt)
> +
> +static int __init bpf_iter_register(void)
> +{
> + struct bpf_iter_reg reg_info = {
> + .target = "ipv6_route",
> + .seq_ops = &ipv6_route_seq_ops,
> + .init_seq_private = bpf_iter_init_seq_net,
> + .fini_seq_private = bpf_iter_fini_seq_net,
> + .seq_priv_size = sizeof(struct ipv6_route_iter),
> + };
> +
> + return bpf_iter_reg_target(®_info);
> +}
> +
> +static void bpf_iter_unregister(void)
> +{
> + bpf_iter_unreg_target("ipv6_route");
Nit. This string duplication is unfortunate. If bpf_iter_unreg_target
took same `struct bpf_iter_ret *` as bpf_iter_reg_target(), it would
be symmetrical and not dependent on magic strings anymore. That
reg_info struct would just be static const struct global variable
passed to both register/unregister.
> +}
> +#endif
> +#endif
> +
[...]
next prev parent reply other threads:[~2020-05-08 19:17 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 5:39 [PATCH bpf-next v3 00/21] bpf: implement bpf iterator for kernel data Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 01/21] bpf: implement an interface to register bpf_iter targets Yonghong Song
2020-05-08 18:18 ` Andrii Nakryiko
2020-05-07 5:39 ` [PATCH bpf-next v3 02/21] bpf: allow loading of a bpf_iter program Yonghong Song
2020-05-08 18:20 ` Andrii Nakryiko
2020-05-07 5:39 ` [PATCH bpf-next v3 03/21] bpf: support bpf tracing/iter programs for BPF_LINK_CREATE Yonghong Song
2020-05-08 18:24 ` Andrii Nakryiko
2020-05-09 1:36 ` Yonghong Song
2020-05-12 3:15 ` Andrii Nakryiko
2020-05-13 16:57 ` Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 04/21] bpf: support bpf tracing/iter programs for BPF_LINK_UPDATE Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 05/21] bpf: implement bpf_seq_read() for bpf iterator Yonghong Song
2020-05-08 18:52 ` Andrii Nakryiko
2020-05-09 1:41 ` Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 06/21] bpf: create anonymous " Yonghong Song
2020-05-08 18:57 ` Andrii Nakryiko
2020-05-07 5:39 ` [PATCH bpf-next v3 07/21] bpf: create file " Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 08/21] bpf: implement common macros/helpers for target iterators Yonghong Song
2020-05-08 19:07 ` Andrii Nakryiko
2020-05-09 3:18 ` Yonghong Song
2020-05-12 3:16 ` Andrii Nakryiko
2020-05-07 5:39 ` [PATCH bpf-next v3 09/21] bpf: add bpf_map iterator Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 10/21] net: bpf: add netlink and ipv6_route bpf_iter targets Yonghong Song
2020-05-08 19:17 ` Andrii Nakryiko [this message]
2020-05-07 5:39 ` [PATCH bpf-next v3 11/21] bpf: add task and task/file iterator targets Yonghong Song
2020-05-08 19:36 ` Andrii Nakryiko
2020-05-07 5:39 ` [PATCH bpf-next v3 12/21] bpf: add PTR_TO_BTF_ID_OR_NULL support Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 13/21] bpf: add bpf_seq_printf and bpf_seq_write helpers Yonghong Song
2020-05-08 19:44 ` Andrii Nakryiko
2020-05-09 4:18 ` Yonghong Song
2020-05-09 5:30 ` Alexei Starovoitov
2020-05-09 6:04 ` Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 14/21] bpf: handle spilled PTR_TO_BTF_ID properly when checking stack_boundary Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 15/21] bpf: support variable length array in tracing programs Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 16/21] tools/libbpf: add bpf_iter support Yonghong Song
2020-05-08 19:46 ` Andrii Nakryiko
2020-05-07 5:39 ` [PATCH bpf-next v3 17/21] tools/libpf: add offsetof/container_of macro in bpf_helpers.h Yonghong Song
2020-05-08 19:48 ` Andrii Nakryiko
2020-05-07 5:39 ` [PATCH bpf-next v3 18/21] tools/bpftool: add bpf_iter support for bptool Yonghong Song
2020-05-08 19:51 ` Andrii Nakryiko
2020-05-09 5:26 ` Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 19/21] tools/bpf: selftests: add iterator programs for ipv6_route and netlink Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 20/21] tools/bpf: selftests: add iter progs for bpf_map/task/task_file Yonghong Song
2020-05-07 5:39 ` [PATCH bpf-next v3 21/21] tools/bpf: selftests: add bpf_iter selftests Yonghong Song
2020-05-08 19:57 ` Andrii Nakryiko
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=CAEf4BzYvwCaG9sTFM-mJXRF-BosuRRe+URZpVUvrke-nXABivA@mail.gmail.com \
--to=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).