From: "Wangnan (F)" <wangnan0@huawei.com>
To: Eric Leblond <eric@regit.org>, <netdev@vger.kernel.org>
Cc: Alexei Starovoitov <ast@fb.com>
Subject: Re: [PATCH net-next 2/2] tools lib bpf: export function to set type
Date: Mon, 15 Aug 2016 11:41:26 +0800 [thread overview]
Message-ID: <57B139E6.8080702@huawei.com> (raw)
In-Reply-To: <1471090643-22403-3-git-send-email-eric@regit.org>
On 2016/8/13 20:17, Eric Leblond wrote:
> Current API was not allowing the user to set a type like socket
> filter. To avoid a setter function for each type, the patch simply
> exports a set function that takes the type in parameter.
>
> Signed-off-by: Eric Leblond <eric@regit.org>
> ---
> tools/lib/bpf/libbpf.c | 15 ++++++---------
> tools/lib/bpf/libbpf.h | 3 +++
> 2 files changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> index 7872ff6..ff2a8c6 100644
> --- a/tools/lib/bpf/libbpf.c
> +++ b/tools/lib/bpf/libbpf.c
> @@ -1336,26 +1336,23 @@ int bpf_program__nth_fd(struct bpf_program *prog, int n)
> return fd;
> }
>
> -static void bpf_program__set_type(struct bpf_program *prog,
> +int bpf_program__set_type(struct bpf_program *prog,
> enum bpf_prog_type type)
> {
> + if (!prog)
> + return -EINVAL;
> prog->type = type;
> + return 0;
> }
>
We'd better add a sanity check here to prevent setting invalid
program type. Plase have a look at
https://lkml.org/lkml/2015/12/17/13
> int bpf_program__set_tracepoint(struct bpf_program *prog)
> {
> - if (!prog)
> - return -EINVAL;
> - bpf_program__set_type(prog, BPF_PROG_TYPE_TRACEPOINT);
> - return 0;
> + return bpf_program__set_type(prog, BPF_PROG_TYPE_TRACEPOINT);
> }
>
> int bpf_program__set_kprobe(struct bpf_program *prog)
> {
> - if (!prog)
> - return -EINVAL;
> - bpf_program__set_type(prog, BPF_PROG_TYPE_KPROBE);
> - return 0;
> + return bpf_program__set_type(prog, BPF_PROG_TYPE_KPROBE);
> }
>
> static bool bpf_program__is_type(struct bpf_program *prog,
> diff --git a/tools/lib/bpf/libbpf.h b/tools/lib/bpf/libbpf.h
> index a6c5cde..6a84d7a 100644
> --- a/tools/lib/bpf/libbpf.h
> +++ b/tools/lib/bpf/libbpf.h
> @@ -173,6 +173,9 @@ int bpf_program__set_kprobe(struct bpf_program *prog);
> bool bpf_program__is_tracepoint(struct bpf_program *prog);
> bool bpf_program__is_kprobe(struct bpf_program *prog);
>
> +int bpf_program__set_type(struct bpf_program *prog,
> + enum bpf_prog_type type);
> +
This makes libbpf.h depend on kernel's uapi/linux/bpf.h.
Although I did this in the above patch, I don't like this
dependency. This is the reason why I introduce
int bpf_program__set_tracepoint(struct bpf_program *prog);
int bpf_program__set_kprobe(struct bpf_program *prog);
bool bpf_program__is_tracepoint(struct bpf_program *prog);
bool bpf_program__is_kprobe(struct bpf_program *prog);
and hide bpf_program__set_type inside the .c file.
Please add type setting functions, or pass int value to
bpf_program__set_type and add sanity checking.
Thank you.
next prev parent reply other threads:[~2016-08-15 3:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 12:17 [PATCH net-next 0/2] libbpf: minor fix and API update Eric Leblond
2016-08-13 12:17 ` [PATCH net-next 1/2] tools lib bpf: suppress useless include Eric Leblond
2016-08-15 3:20 ` Wangnan (F)
2016-08-13 12:17 ` [PATCH net-next 2/2] tools lib bpf: export function to set type Eric Leblond
2016-08-15 3:41 ` Wangnan (F) [this message]
2016-08-15 1:22 ` [PATCH net-next 0/2] libbpf: minor fix and API update Wangnan (F)
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=57B139E6.8080702@huawei.com \
--to=wangnan0@huawei.com \
--cc=ast@fb.com \
--cc=eric@regit.org \
--cc=netdev@vger.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 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.