[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200312233845.oehxavap4aapofst@kafai-mbp>
Date: Thu, 12 Mar 2020 16:38:45 -0700
From: Martin KaFai Lau <kafai@...com>
To: Andrii Nakryiko <andriin@...com>
CC: <bpf@...r.kernel.org>, <netdev@...r.kernel.org>, <ast@...com>,
<daniel@...earbox.net>, <andrii.nakryiko@...il.com>,
<kernel-team@...com>
Subject: Re: [PATCH bpf-next] bpf: abstract away entire bpf_link clean up
procedure
On Thu, Mar 12, 2020 at 01:39:14PM -0700, Andrii Nakryiko wrote:
> Instead of requiring users to do three steps for cleaning up bpf_link, its
> anon_inode file, and unused fd, abstract that away into bpf_link_cleanup()
> helper. bpf_link_defunct() is removed, as it shouldn't be needed as an
> individual operation anymore.
>
> Signed-off-by: Andrii Nakryiko <andriin@...com>
> ---
> include/linux/bpf.h | 3 ++-
> kernel/bpf/syscall.c | 18 +++++++++++-------
Changes are only in syscall.c. Should bpf_link_cleanup() be static?
Powered by blists - more mailing lists