linux-kernel - Re: [PATCH] tools/bpftool: Fix error return code in do

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6cb1dfd7-6456-ef1c-d708-042ab53b3d2c@iogearbox.net>
Date:   Wed, 15 Jul 2020 21:23:33 +0200
From:   Daniel Borkmann <daniel@...earbox.net>
To:     YueHaibing <yuehaibing@...wei.com>, ast@...nel.org, kafai@...com,
        songliubraving@...com, yhs@...com, andriin@...com,
        john.fastabend@...il.com, kpsingh@...omium.org
Cc:     netdev@...r.kernel.org, bpf@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tools/bpftool: Fix error return code in do_skeleton()

On 7/15/20 5:13 AM, YueHaibing wrote:
> The error return code should be PTR_ERR(obj) other than
> PTR_ERR(NULL).
> 
> Fixes: 5dc7a8b21144 ("bpftool, selftests/bpf: Embed object file inside skeleton")
> Signed-off-by: YueHaibing <yuehaibing@...wei.com>
> ---
>   tools/bpf/bpftool/gen.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/bpf/bpftool/gen.c b/tools/bpf/bpftool/gen.c
> index 10de76b296ba..35f62273cdbd 100644
> --- a/tools/bpf/bpftool/gen.c
> +++ b/tools/bpf/bpftool/gen.c
> @@ -305,8 +305,9 @@ static int do_skeleton(int argc, char **argv)
>   	opts.object_name = obj_name;
>   	obj = bpf_object__open_mem(obj_data, file_sz, &opts);
>   	if (IS_ERR(obj)) {
> +		err = PTR_ERR(obj);
> +		p_err("failed to open BPF object file: %ld", err);
>   		obj = NULL;
> -		p_err("failed to open BPF object file: %ld", PTR_ERR(obj));
>   		goto out;

Instead of just the error number, could we dump something useful to the user here
via libbpf_strerror() given you touch this line? Also, I think the convention in
do_skeleton() is to just return {0,-1} given this is propagated as return code
for bpftool.

>   	}
>   
>