From: Martin KaFai Lau <martin.lau@linux.dev>
To: Kui-Feng Lee <thinker.li@gmail.com>, andrii@kernel.org
Cc: sinquersw@gmail.com, kuifeng@meta.com, bpf@vger.kernel.org,
ast@kernel.org, song@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next 1/2] bpf: enable the "open" operator on a pinned path of a struct_osp link.
Date: Fri, 19 Apr 2024 17:05:53 -0700 [thread overview]
Message-ID: <8dadfcc9-1f6a-4b93-951b-548e4560ce5a@linux.dev> (raw)
In-Reply-To: <20240417002513.1534535-2-thinker.li@gmail.com>
On 4/16/24 5:25 PM, Kui-Feng Lee wrote:
> +int bpffs_struct_ops_link_open(struct inode *inode, struct file *filp)
> +{
> + struct bpf_struct_ops_link *link = inode->i_private;
> +
> + /* Paired with bpf_link_put_direct() in bpf_link_release(). */
> + bpf_link_inc(&link->link);
> + filp->private_data = link;
> + return 0;
> +}
> diff --git a/kernel/bpf/inode.c b/kernel/bpf/inode.c
> index af5d2ffadd70..b020d761ab0a 100644
> --- a/kernel/bpf/inode.c
> +++ b/kernel/bpf/inode.c
> @@ -360,11 +360,16 @@ static int bpf_mkmap(struct dentry *dentry, umode_t mode, void *arg)
>
> static int bpf_mklink(struct dentry *dentry, umode_t mode, void *arg)
> {
> + const struct file_operations *fops;
> struct bpf_link *link = arg;
>
> - return bpf_mkobj_ops(dentry, mode, arg, &bpf_link_iops,
> - bpf_link_is_iter(link) ?
> - &bpf_iter_fops : &bpffs_obj_fops);
> + if (bpf_link_is_iter(link))
> + fops = &bpf_iter_fops;
> + else if (link->type == BPF_LINK_TYPE_STRUCT_OPS)
Open a pinned link and then update should not be specific to struct_ops link.
e.g. should be useful to the cgroup link also?
Andrii, wdyt about supporting other link types also?
> + fops = &bpf_link_fops;
> + else
> + fops = &bpffs_obj_fops;
> + return bpf_mkobj_ops(dentry, mode, arg, &bpf_link_iops, fops);
> }
>
> static struct dentry *
> diff --git a/kernel/bpf/syscall.c b/kernel/bpf/syscall.c
> index 7d392ec83655..f66bc6215faa 100644
> --- a/kernel/bpf/syscall.c
> +++ b/kernel/bpf/syscall.c
> @@ -3108,7 +3108,19 @@ static void bpf_link_show_fdinfo(struct seq_file *m, struct file *filp)
> }
> #endif
>
> -static const struct file_operations bpf_link_fops = {
> +/* Support opening pinned links */
> +static int bpf_link_open(struct inode *inode, struct file *filp)
> +{
> + struct bpf_link *link = inode->i_private;
> +
> + if (link->type == BPF_LINK_TYPE_STRUCT_OPS)
> + return bpffs_struct_ops_link_open(inode, filp);
> +
> + return -EOPNOTSUPP;
> +}
> +
> +const struct file_operations bpf_link_fops = {
> + .open = bpf_link_open,
> #ifdef CONFIG_PROC_FS
> .show_fdinfo = bpf_link_show_fdinfo,
> #endif
next prev parent reply other threads:[~2024-04-20 0:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 0:25 [PATCH bpf-next 0/2] Update a struct_ops link through a pinned path Kui-Feng Lee
2024-04-17 0:25 ` [PATCH bpf-next 1/2] bpf: enable the "open" operator on a pinned path of a struct_osp link Kui-Feng Lee
2024-04-17 23:19 ` kernel test robot
2024-04-18 6:13 ` kernel test robot
2024-04-20 0:05 ` Martin KaFai Lau [this message]
2024-04-22 17:12 ` Kui-Feng Lee
2024-04-22 17:30 ` Kui-Feng Lee
2024-04-22 23:43 ` Martin KaFai Lau
2024-04-23 17:16 ` Kui-Feng Lee
2024-04-24 0:29 ` Martin KaFai Lau
2024-04-25 0:17 ` Andrii Nakryiko
2024-04-25 17:11 ` Kui-Feng Lee
2024-04-17 0:25 ` [PATCH bpf-next 2/2] selftests/bpf: open a pinned path of a struct_ops link Kui-Feng Lee
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=8dadfcc9-1f6a-4b93-951b-548e4560ce5a@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=sinquersw@gmail.com \
--cc=song@kernel.org \
--cc=thinker.li@gmail.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