From: Hangbin Liu <haliu@redhat.com>
To: Paul Chaignon <paul@isovalent.com>
Cc: netdev@vger.kernel.org,
Stephen Hemminger <stephen@networkplumber.org>,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH iproute2] lib/bpf: fix verbose flag when using libbpf
Date: Fri, 17 Dec 2021 15:15:31 +0800 [thread overview]
Message-ID: <Ybw5EwPCzZXeaWip@Laptop-X1> (raw)
In-Reply-To: <20211216153336.GA30454@Mem>
On Thu, Dec 16, 2021 at 04:33:36PM +0100, Paul Chaignon wrote:
> Since commit 6d61a2b55799 ("lib: add libbpf support"), passing the
> verbose flag to tc filter doesn't dump the verifier logs anymore in case
> of successful loading.
>
> This commit fixes it by setting the log_level attribute before loading.
> To that end, we need to call bpf_object__load_xattr directly instead of
> relying on bpf_object__load.
>
> Fixes: 6d61a2b55799 ("lib: add libbpf support")
> Signed-off-by: Paul Chaignon <paul@isovalent.com>
> ---
> lib/bpf_libbpf.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/lib/bpf_libbpf.c b/lib/bpf_libbpf.c
> index dbec2cb5..b992a62c 100644
> --- a/lib/bpf_libbpf.c
> +++ b/lib/bpf_libbpf.c
> @@ -246,6 +246,7 @@ static int handle_legacy_maps(struct bpf_object *obj)
>
> static int load_bpf_object(struct bpf_cfg_in *cfg)
> {
> + struct bpf_object_load_attr attr = {};
> struct bpf_program *p, *prog = NULL;
> struct bpf_object *obj;
> char root_path[PATH_MAX];
> @@ -302,7 +303,11 @@ static int load_bpf_object(struct bpf_cfg_in *cfg)
> if (ret)
> goto unload_obj;
>
> - ret = bpf_object__load(obj);
> + attr.obj = obj;
> + if (cfg->verbose) {
> + attr.log_level = 2;
> + }
nit: no need the curly braces when this is only 1 line
> + ret = bpf_object__load_xattr(&attr);
> if (ret)
> goto unload_obj;
>
Thanks for the fixes.
Acked-by: Hangbin Liu <haliu@redhat.com>
prev parent reply other threads:[~2021-12-17 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 15:33 [PATCH iproute2] lib/bpf: fix verbose flag when using libbpf Paul Chaignon
2021-12-17 7:15 ` Hangbin Liu [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=Ybw5EwPCzZXeaWip@Laptop-X1 \
--to=haliu@redhat.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=paul@isovalent.com \
--cc=stephen@networkplumber.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 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).