From: Eduard Zingerman <eddyz87@gmail.com>
To: Kui-Feng Lee <thinker.li@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
song@kernel.org, kernel-team@meta.com, andrii@kernel.org
Cc: sinquersw@gmail.com, kuifeng@meta.com
Subject: Re: [PATCH bpf-next v2 0/2] Update a struct_ops link through a pinned path
Date: Thu, 18 Apr 2024 14:37:21 -0700 [thread overview]
Message-ID: <e504821b4570a9b94c16da88cb6a632a73e4d204.camel@gmail.com> (raw)
In-Reply-To: <20240418163509.719335-1-thinker.li@gmail.com>
On Thu, 2024-04-18 at 09:35 -0700, Kui-Feng Lee wrote:
> Applications already have the ability to update a struct_ops link with
> another struct_ops map. However, they were unable to open pinned paths
> of the links. This implies that updating a link through its pinned
> paths was not feasible. By allowing the "open" operator on pinned
> paths, applications can pin a struct_ops link and update the link
> through the pinned path later.
>
> ---
Not an expert in how bpffs is tied together, but this patch-set seems to be fine.
Reviewed-by: Eduard Zingerman <eddyz87@gmail.com>
prev parent reply other threads:[~2024-04-18 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 16:35 [PATCH bpf-next v2 0/2] Update a struct_ops link through a pinned path Kui-Feng Lee
2024-04-18 16:35 ` [PATCH bpf-next v2 1/2] bpf: enable the "open" operator on a pinned path of a struct_osp link Kui-Feng Lee
2024-04-25 0:09 ` Andrii Nakryiko
2024-04-18 16:35 ` [PATCH bpf-next v2 2/2] selftests/bpf: open a pinned path of a struct_ops link Kui-Feng Lee
2024-04-18 21:37 ` Eduard Zingerman [this message]
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=e504821b4570a9b94c16da88cb6a632a73e4d204.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--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