From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com
Cc: Mykyta Yatsenko <yatsenko@meta.com>
Subject: Re: [PATCH bpf v3 0/2] bpf: add _impl suffix for kfuncs with implicit args
Date: Tue, 4 Nov 2025 15:08:42 -0800 [thread overview]
Message-ID: <d0c4f896-c520-4ea1-92fd-fa151dc0c57d@linux.dev> (raw)
In-Reply-To: <20251104-implv2-v3-0-4772b9ae0e06@meta.com>
On 11/4/25 2:54 PM, Mykyta Yatsenko wrote:
> We have established a pattern of function naming win "_impl" suffix;
> those functions accept verifier-provided bpf_prog_aux argument.
> Following uniform convention will allow for transparent backwards
> compatibility with the upcoming KF_IMPLICIT_ARGS feature. This patch
> set aims to fix current deviation from the convention to eliminate
> unnecessary backwards incompatibility in the future.
>
> Three kfuncs added in 6.18 don’t follow this *_impl convention and
> therefore won’t participate in the new KF_IMPLICIT_ARGS mechanism:
> * bpf_task_work_schedule_resume()
> * bpf_task_work_schedule_signal()
> * bpf_stream_vprintk()
>
> Rename them to align with the implicit-arg flow:
> bpf_task_work_schedule_resume() -> bpf_task_work_schedule_resume_impl()
> bpf_task_work_schedule_signal() -> bpf_task_work_schedule_signal_impl()
> bpf_stream_vprintk() -> bpf_stream_vprintk_impl()
>
> The KF_IMPLICIT_ARGS mechanism is not in tree yet, so callers must
> switch to the *_impl names for now. Once the new mechanism lands, the
> plain names (without _impl) will be reintroduced.
>
> Signed-off-by: Mykyta Yatsenko <yatsenko@meta.com>
Acked-by: Ihor Solodrai <ihor.solodrai@linux.dev>
Thanks!
> ---
> Changes in v3:
> - Fix commit messages
> - Link to v2: https://lore.kernel.org/r/20251104-implv2-v2-0-6dbc35f39f28@meta.com
>
> Changes in v1:
> - Split commit into 2
> - Rebase on the correct branch
> - Link to v1: https://lore.kernel.org/all/20251103232319.122965-1-mykyta.yatsenko5@gmail.com/
>
> ---
> Mykyta Yatsenko (2):
> bpf:add _impl suffix for bpf_task_work_schedule* kfuncs
> bpf: add _impl suffix for bpf_stream_vprintk() kfunc
>
> kernel/bpf/helpers.c | 26 +++++++++++---------
> kernel/bpf/stream.c | 3 ++-
> kernel/bpf/verifier.c | 12 +++++-----
> tools/bpf/bpftool/Documentation/bpftool-prog.rst | 2 +-
> tools/lib/bpf/bpf_helpers.h | 28 +++++++++++-----------
> tools/testing/selftests/bpf/progs/stream_fail.c | 6 ++---
> tools/testing/selftests/bpf/progs/task_work.c | 6 ++---
> tools/testing/selftests/bpf/progs/task_work_fail.c | 8 +++----
> .../testing/selftests/bpf/progs/task_work_stress.c | 4 ++--
> 9 files changed, 50 insertions(+), 45 deletions(-)
> ---
> base-commit: 6146a0f1dfae5d37442a9ddcba012add260bceb0
> change-id: 20251104-implv2-d6c4be255026
>
> Best regards,
next prev parent reply other threads:[~2025-11-04 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 22:54 [PATCH bpf v3 0/2] bpf: add _impl suffix for kfuncs with implicit args Mykyta Yatsenko
2025-11-04 22:54 ` [PATCH bpf v3 1/2] bpf:add _impl suffix for bpf_task_work_schedule* kfuncs Mykyta Yatsenko
2025-11-04 22:54 ` [PATCH bpf v3 2/2] bpf: add _impl suffix for bpf_stream_vprintk() kfunc Mykyta Yatsenko
2025-11-04 23:08 ` Ihor Solodrai [this message]
2025-11-05 2:00 ` [PATCH bpf v3 0/2] bpf: add _impl suffix for kfuncs with implicit args patchwork-bot+netdevbpf
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=d0c4f896-c520-4ea1-92fd-fa151dc0c57d@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=yatsenko@meta.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