linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: Wang Hai <wanghai38@huawei.com>,
	quentin@isovalent.com, mrostecki@opensuse.org,
	john.fastabend@gmail.com
Cc: ast@kernel.org, daniel@iogearbox.net, kafai@fb.com,
	songliubraving@fb.com, yhs@fb.com, andrii@kernel.org,
	kpsingh@chromium.org, toke@redhat.com, danieltimlee@gmail.com,
	bpf@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: RE: [PATCH v2 bpf] tools: bpftool: Add missing close before bpftool net attach exit
Date: Mon, 09 Nov 2020 20:33:53 -0800	[thread overview]
Message-ID: <5faa18319b71_3e187208f@john-XPS-13-9370.notmuch> (raw)
In-Reply-To: <20201110014637.6055-1-wanghai38@huawei.com>

Wang Hai wrote:
> progfd is created by prog_parse_fd(), before 'bpftool net attach' exit,
> it should be closed.
> 
> Fixes: 04949ccc273e ("tools: bpftool: add net attach command to attach XDP on interface")
> Signed-off-by: Wang Hai <wanghai38@huawei.com>
> ---
> v1->v2: use cleanup tag instead of repeated closes
>  tools/bpf/bpftool/net.c | 14 ++++++++------
>  1 file changed, 8 insertions(+), 6 deletions(-)
> 
> diff --git a/tools/bpf/bpftool/net.c b/tools/bpf/bpftool/net.c
> index 910e7bac6e9e..1ac7228167e6 100644
> --- a/tools/bpf/bpftool/net.c
> +++ b/tools/bpf/bpftool/net.c
> @@ -578,8 +578,8 @@ static int do_attach(int argc, char **argv)
>  
>  	ifindex = net_parse_dev(&argc, &argv);
>  	if (ifindex < 1) {
> -		close(progfd);
> -		return -EINVAL;
> +		err = -EINVAL;
> +		goto cleanup;
>  	}
>  
>  	if (argc) {
> @@ -587,8 +587,8 @@ static int do_attach(int argc, char **argv)
>  			overwrite = true;
>  		} else {
>  			p_err("expected 'overwrite', got: '%s'?", *argv);
> -			close(progfd);
> -			return -EINVAL;
> +			err = -EINVAL;
> +			goto cleanup;
>  		}
>  	}
>  
> @@ -600,13 +600,15 @@ static int do_attach(int argc, char **argv)

I think now that return value depends on this err it should be 'if (err)'
otherwise we risk retunring non-zero error code from do_attach which
will cause programs to fail.

>  	if (err < 0) {
        ^^^^^^^^^^^^
        if (err) {

>  		p_err("interface %s attach failed: %s",
>  		      attach_type_strings[attach_type], strerror(-err));
> -		return err;
> +		goto cleanup;
>  	}
>  
>  	if (json_output)
>  		jsonw_null(json_wtr);
>  
> -	return 0;


Alternatively we could add an 'err = 0' here, but above should never
return a value >0 as far as I can see.

Thanks,
John

> +cleanup:
> +	close(progfd);
> +	return err;
>  }
>  
>  static int do_detach(int argc, char **argv)
> -- 
> 2.17.1
> 



  reply	other threads:[~2020-11-10  4:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10  1:46 [PATCH v2 bpf] tools: bpftool: Add missing close before bpftool net attach exit Wang Hai
2020-11-10  4:33 ` John Fastabend [this message]
2020-11-10  8:40   ` wanghai (M)
2020-11-11  8:44     ` John Fastabend

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=5faa18319b71_3e187208f@john-XPS-13-9370.notmuch \
    --to=john.fastabend@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=danieltimlee@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrostecki@opensuse.org \
    --cc=netdev@vger.kernel.org \
    --cc=quentin@isovalent.com \
    --cc=songliubraving@fb.com \
    --cc=toke@redhat.com \
    --cc=wanghai38@huawei.com \
    --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).