bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Andrii Nakryiko <andriin@fb.com>,
	bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com
Cc: andrii.nakryiko@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next] bpf: add bpf_link_new_file that doesn't install FD
Date: Wed, 11 Mar 2020 14:22:05 +0100	[thread overview]
Message-ID: <7467529c-b712-5314-ebbe-13f73ac01bdb@iogearbox.net> (raw)
In-Reply-To: <20200309231051.1270337-1-andriin@fb.com>

On 3/10/20 12:10 AM, Andrii Nakryiko wrote:
> Add bpf_link_new_file() API for cases when we need to ensure anon_inode is
> successfully created before we proceed with expensive BPF program attachment
> procedure, which will require equally (if not more so) expensive and
> potentially failing compensation detachment procedure just because anon_inode
> creation failed. This API allows to simplify code by ensuring first that
> anon_inode is created and after BPF program is attached proceed with
> fd_install() that can't fail.
> 
> After anon_inode file is created, link can't be just kfree()'d anymore,
> because its destruction will be performed by deferred file_operations->release
> call. For this, bpf_link API required specifying two separate operations:
> release() and dealloc(), former performing detachment only, while the latter
> frees memory used by bpf_link itself. dealloc() needs to be specified, because
> struct bpf_link is frequently embedded into link type-specific container
> struct (e.g., struct bpf_raw_tp_link), so bpf_link itself doesn't know how to
> properly free the memory. In case when anon_inode file was successfully
> created, but subsequent BPF attachment failed, bpf_link needs to be marked as
> "defunct", so that file's release() callback will perform only memory
> deallocation, but no detachment.
> 
> Convert raw tracepoint and tracing attachment to new API and eliminate
> detachment from error handling path.
> 
> Signed-off-by: Andrii Nakryiko <andriin@fb.com>

Applied, but ...

[...]
> @@ -2337,20 +2374,24 @@ static int bpf_tracing_prog_attach(struct bpf_prog *prog)
>   	}
>   	bpf_link_init(&link->link, &bpf_tracing_link_lops, prog);
>   
> -	err = bpf_trampoline_link_prog(prog);
> -	if (err)
> -		goto out_free_link;
> +	link_file = bpf_link_new_file(&link->link, &link_fd);
> +	if (IS_ERR(link_file)) {
> +		kfree(link);
> +		err = PTR_ERR(link_file);
> +		goto out_put_prog;
> +	}
>   
> -	link_fd = bpf_link_new_fd(&link->link);
> -	if (link_fd < 0) {
> -		WARN_ON_ONCE(bpf_trampoline_unlink_prog(prog));
> -		err = link_fd;
> -		goto out_free_link;
> +	err = bpf_trampoline_link_prog(prog);
> +	if (err) {
> +		bpf_link_defunct(&link->link);
> +		fput(link_file);
> +		put_unused_fd(link_fd);

Given the tear-down in error case requires 3 manual steps here, I think this begs
for a small helper.

> +		goto out_put_prog;
>   	}
> +
> +	fd_install(link_fd, link_file);
>   	return link_fd;
>   
[...]
> @@ -2431,28 +2481,32 @@ static int bpf_raw_tracepoint_open(const union bpf_attr *attr)
>   		goto out_put_prog;
>   	}
>   
[...]
>   
> -	link_fd = bpf_link_new_fd(&raw_tp->link);
> -	if (link_fd < 0) {
> -		bpf_probe_unregister(raw_tp->btp, prog);
> -		err = link_fd;
> -		goto out_free_tp;
> +	err = bpf_probe_register(link->btp, prog);
> +	if (err) {
> +		bpf_link_defunct(&link->link);
> +		fput(link_file);
> +		put_unused_fd(link_fd);

Especially since you need it in multiple places; please follow-up.

> +		goto out_put_btp;
>   	}
> +
> +	fd_install(link_fd, link_file);
>   	return link_fd;
>   
> -out_free_tp:
> -	kfree(raw_tp);
>   out_put_btp:
>   	bpf_put_raw_tracepoint(btp);
>   out_put_prog:
> 


  parent reply	other threads:[~2020-03-11 13:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09 23:10 [PATCH bpf-next] bpf: add bpf_link_new_file that doesn't install FD Andrii Nakryiko
2020-03-10 21:45 ` John Fastabend
2020-03-11 13:22 ` Daniel Borkmann [this message]
2020-03-11 15:21   ` Andrii Nakryiko

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=7467529c-b712-5314-ebbe-13f73ac01bdb@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andriin@fb.com \
    --cc=ast@fb.com \
    --cc=bpf@vger.kernel.org \
    --cc=kernel-team@fb.com \
    --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 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).