[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <796E4DA8-4844-4708-866E-A8AE9477E94E@fb.com>
Date: Thu, 29 Aug 2019 20:02:32 +0000
From: Song Liu <songliubraving@...com>
To: Anton Protopopov <a.s.protopopov@...il.com>
CC: Andrii Nakryiko <andriin@...com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Martin Lau <kafai@...com>, "Yonghong Song" <yhs@...com>,
Networking <netdev@...r.kernel.org>, bpf <bpf@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH bpf-next] tools: libbpf: update extended attributes
version of bpf_object__open()
> On Aug 14, 2019, at 5:03 PM, Anton Protopopov <a.s.protopopov@...il.com> wrote:
>
[...]
>
>
> int bpf_object__unload(struct bpf_object *obj)
> diff --git a/tools/lib/bpf/libbpf.h b/tools/lib/bpf/libbpf.h
> index e8f70977d137..634f278578dd 100644
> --- a/tools/lib/bpf/libbpf.h
> +++ b/tools/lib/bpf/libbpf.h
> @@ -63,8 +63,13 @@ LIBBPF_API libbpf_print_fn_t libbpf_set_print(libbpf_print_fn_t fn);
> struct bpf_object;
>
> struct bpf_object_open_attr {
> - const char *file;
> + union {
> + const char *file;
> + const char *obj_name;
> + };
> enum bpf_prog_type prog_type;
> + void *obj_buf;
> + size_t obj_buf_sz;
> };
I think this would break dynamically linked libbpf. No?
Thanks,
Song
Powered by blists - more mailing lists