From: Leon Hwang <leon.hwang@linux.dev>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
Christian Brauner <brauner@kernel.org>,
Seth Forshee <sforshee@kernel.org>,
Yuichiro Tsuji <yuichtsu@amazon.com>,
Andrey Albershteyn <aalbersh@redhat.com>,
Willem de Bruijn <willemb@google.com>,
Jason Xing <kerneljasonxing@gmail.com>,
Tao Chen <chen.dylane@linux.dev>,
Mykyta Yatsenko <yatsenko@meta.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Anton Protopopov <a.s.protopopov@gmail.com>,
Amery Hung <ameryhung@gmail.com>, Rong Tao <rongtao@cestc.cn>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
linux-kselftest@vger.kernel.org, kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next v5 2/9] libbpf: Add support for extended bpf syscall
Date: Fri, 16 Jan 2026 21:57:47 +0800 [thread overview]
Message-ID: <3b0fa14d-a11d-4ed7-8f28-2e99d74f6b46@linux.dev> (raw)
In-Reply-To: <CAEf4BzYRC+=J05C6QDwgzbJ7gO7gZD4xcEcj9ixCaJ=xaRuSsQ@mail.gmail.com>
On 2026/1/16 08:42, Andrii Nakryiko wrote:
> On Mon, Jan 12, 2026 at 6:58 AM Leon Hwang <leon.hwang@linux.dev> wrote:
>>
>> To support the extended BPF syscall introduced in the previous commit,
>> introduce the following internal APIs:
>>
>> * 'sys_bpf_ext()'
>> * 'sys_bpf_ext_fd()'
>> They wrap the raw 'syscall()' interface to support passing extended
>> attributes.
>> * 'probe_sys_bpf_ext()'
>> Check whether current kernel supports the extended attributes.
>>
>> Signed-off-by: Leon Hwang <leon.hwang@linux.dev>
>> ---
>> tools/lib/bpf/bpf.c | 34 +++++++++++++++++++++++++++++++++
>> tools/lib/bpf/features.c | 8 ++++++++
>> tools/lib/bpf/libbpf_internal.h | 3 +++
>> 3 files changed, 45 insertions(+)
>>
>> diff --git a/tools/lib/bpf/bpf.c b/tools/lib/bpf/bpf.c
>> index 21b57a629916..d44e667aaf02 100644
>> --- a/tools/lib/bpf/bpf.c
>> +++ b/tools/lib/bpf/bpf.c
>> @@ -69,6 +69,40 @@ static inline __u64 ptr_to_u64(const void *ptr)
>> return (__u64) (unsigned long) ptr;
>> }
>>
>> +static inline int sys_bpf_ext(enum bpf_cmd cmd, union bpf_attr *attr,
>> + unsigned int size,
>> + struct bpf_common_attr *common_attr,
>
> nit: kernel uses consistent attr_common/size_common pattern, but here
> you are inverting attr_common -> common_attr, let's not?
>
Ack.
I'll keep the same pattern.
>> + unsigned int size_common)
>> +{
>> + cmd = common_attr ? (cmd | BPF_COMMON_ATTRS) : (cmd & ~BPF_COMMON_ATTRS);
>> + return syscall(__NR_bpf, cmd, attr, size, common_attr, size_common);
>> +}
>> +
>> +static inline int sys_bpf_ext_fd(enum bpf_cmd cmd, union bpf_attr *attr,
>> + unsigned int size,
>> + struct bpf_common_attr *common_attr,
>> + unsigned int size_common)
>> +{
>> + int fd;
>> +
>> + fd = sys_bpf_ext(cmd, attr, size, common_attr, size_common);
>> + return ensure_good_fd(fd);
>> +}
>> +
>> +int probe_sys_bpf_ext(void)
>> +{
>> + const size_t attr_sz = offsetofend(union bpf_attr, prog_token_fd);
>> + union bpf_attr attr;
>> + int fd;
>> +
>> + memset(&attr, 0, attr_sz);
>> + fd = syscall(__NR_bpf, BPF_PROG_LOAD | BPF_COMMON_ATTRS, &attr, attr_sz, NULL,
>> + sizeof(struct bpf_common_attr));
>> + if (fd >= 0)
>> + close(fd);
>
> hm... close can change errno, this is fragile. If fd >= 0, something
> is wrong with our detection, just return error right away?
>
How about capture errno before closing?
err = errno;
if (fd >= 0)
close(fd);
return err = EFAULT;
Then, we can wrap all details in probe_sys_bpf_ext().
>> + return errno == EFAULT;
>> +}
>> +
>> static inline int sys_bpf(enum bpf_cmd cmd, union bpf_attr *attr,
>> unsigned int size)
>> {
>> diff --git a/tools/lib/bpf/features.c b/tools/lib/bpf/features.c
>> index b842b83e2480..d786a815f1ae 100644
>> --- a/tools/lib/bpf/features.c
>> +++ b/tools/lib/bpf/features.c
>> @@ -506,6 +506,11 @@ static int probe_kern_arg_ctx_tag(int token_fd)
>> return probe_fd(prog_fd);
>> }
>>
>> +static int probe_kern_extended_syscall(int token_fd)
>> +{
>> + return probe_sys_bpf_ext();
>> +}
>> +
>> typedef int (*feature_probe_fn)(int /* token_fd */);
>>
>> static struct kern_feature_cache feature_cache;
>> @@ -581,6 +586,9 @@ static struct kern_feature_desc {
>> [FEAT_BTF_QMARK_DATASEC] = {
>> "BTF DATASEC names starting from '?'", probe_kern_btf_qmark_datasec,
>> },
>> + [FEAT_EXTENDED_SYSCALL] = {
>> + "Kernel supports extended syscall", probe_kern_extended_syscall,
>
> "extended syscall" is a bit vague... We specifically detect common
> attrs support, maybe say that?
>
Ack.
I'll update it to "BPF syscall common attributes support."
>> + },
>> };
>>
>> bool feat_supported(struct kern_feature_cache *cache, enum kern_feature_id feat_id)
>> diff --git a/tools/lib/bpf/libbpf_internal.h b/tools/lib/bpf/libbpf_internal.h
>> index fc59b21b51b5..e2a6ef4b45ae 100644
>> --- a/tools/lib/bpf/libbpf_internal.h
>> +++ b/tools/lib/bpf/libbpf_internal.h
>> @@ -392,6 +392,8 @@ enum kern_feature_id {
>> FEAT_ARG_CTX_TAG,
>> /* Kernel supports '?' at the front of datasec names */
>> FEAT_BTF_QMARK_DATASEC,
>> + /* Kernel supports extended syscall */
>> + FEAT_EXTENDED_SYSCALL,
>
> FEAT_BPF_COMMON_ATTRS ?
>
FEAT_BPF_SYSCALL_COMMON_ATTRS seems more accurate.
Thanks,
Leon
>> __FEAT_CNT,
>> };
>>
>> @@ -757,4 +759,5 @@ int probe_fd(int fd);
>> #define SHA256_DWORD_SIZE SHA256_DIGEST_LENGTH / sizeof(__u64)
>>
>> void libbpf_sha256(const void *data, size_t len, __u8 out[SHA256_DIGEST_LENGTH]);
>> +int probe_sys_bpf_ext(void);
>> #endif /* __LIBBPF_LIBBPF_INTERNAL_H */
>> --
>> 2.52.0
>>
next prev parent reply other threads:[~2026-01-16 13:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 14:56 [PATCH bpf-next v5 0/9] bpf: Extend BPF syscall with common attributes support Leon Hwang
2026-01-12 14:56 ` [PATCH bpf-next v5 1/9] " Leon Hwang
2026-01-12 14:56 ` [PATCH bpf-next v5 2/9] libbpf: Add support for extended bpf syscall Leon Hwang
2026-01-16 0:42 ` Andrii Nakryiko
2026-01-16 13:57 ` Leon Hwang [this message]
2026-01-16 22:27 ` Andrii Nakryiko
2026-01-12 14:56 ` [PATCH bpf-next v5 3/9] bpf: Refactor reporting log_true_size for prog_load Leon Hwang
2026-01-12 14:56 ` [PATCH bpf-next v5 4/9] bpf: Add syscall common attributes support " Leon Hwang
2026-01-16 0:54 ` Andrii Nakryiko
2026-01-16 14:10 ` Leon Hwang
2026-01-16 22:29 ` Andrii Nakryiko
2026-01-12 14:56 ` [PATCH bpf-next v5 5/9] bpf: Refactor reporting btf_log_true_size for btf_load Leon Hwang
2026-01-12 14:56 ` [PATCH bpf-next v5 6/9] bpf: Add syscall common attributes support " Leon Hwang
2026-01-12 14:56 ` [PATCH bpf-next v5 7/9] bpf: Add syscall common attributes support for map_create Leon Hwang
2026-01-12 14:56 ` [PATCH bpf-next v5 8/9] libbpf: Add common attr " Leon Hwang
2026-01-16 1:03 ` Andrii Nakryiko
2026-01-16 14:17 ` Leon Hwang
2026-01-16 22:33 ` Andrii Nakryiko
2026-01-12 14:56 ` [PATCH bpf-next v5 9/9] selftests/bpf: Add tests to verify map create failure log Leon Hwang
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=3b0fa14d-a11d-4ed7-8f28-2e99d74f6b46@linux.dev \
--to=leon.hwang@linux.dev \
--cc=a.s.protopopov@gmail.com \
--cc=aalbersh@redhat.com \
--cc=ameryhung@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=chen.dylane@linux.dev \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-patches-bot@fb.com \
--cc=kerneljasonxing@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=rongtao@cestc.cn \
--cc=sdf@fomichev.me \
--cc=sforshee@kernel.org \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=willemb@google.com \
--cc=yatsenko@meta.com \
--cc=yonghong.song@linux.dev \
--cc=yuichtsu@amazon.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