From: Leon Hwang <leon.hwang@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf <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>,
LKML <linux-kernel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next v7 2/9] libbpf: Add support for extended bpf syscall
Date: Fri, 23 Jan 2026 12:06:45 +0800 [thread overview]
Message-ID: <a0ce1dab-7d7e-4b04-a033-4f0611090d34@linux.dev> (raw)
In-Reply-To: <CAADnVQJLz+nMHCZXUgy2MOxwFczEHNbG8ZUgfZeUY4yXFUKcNw@mail.gmail.com>
On 23/1/26 11:55, Alexei Starovoitov wrote:
> On Thu, Jan 22, 2026 at 7:25 PM Leon Hwang <leon.hwang@linux.dev> wrote:
>>
>>
>> +static int probe_bpf_syscall_common_attrs(int token_fd)
>> +{
>> + int ret;
>> +
>> + ret = probe_sys_bpf_ext();
>> + return ret > 0;
>> +}
>
> When you look at the above, what thoughts come to mind?
>
> ... and please don't use ai for answers.
My initial thought was whether probe_fd() is needed here to handle and
close a returned fd, since the return value of probe_sys_bpf_ext() isn’t
obvious from the call site.
Thanks,
Leon
next prev parent reply other threads:[~2026-01-23 4:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 3:24 [PATCH bpf-next v7 0/9] bpf: Extend BPF syscall with common attributes support Leon Hwang
2026-01-23 3:24 ` [PATCH bpf-next v7 1/9] " Leon Hwang
2026-01-23 3:24 ` [PATCH bpf-next v7 2/9] libbpf: Add support for extended bpf syscall Leon Hwang
2026-01-23 3:55 ` Alexei Starovoitov
2026-01-23 4:06 ` Leon Hwang [this message]
2026-01-23 4:12 ` Alexei Starovoitov
2026-01-23 4:19 ` Leon Hwang
2026-01-23 18:52 ` Andrii Nakryiko
2026-01-26 2:03 ` Leon Hwang
2026-01-23 3:24 ` [PATCH bpf-next v7 3/9] bpf: Refactor reporting log_true_size for prog_load Leon Hwang
2026-01-23 3:24 ` [PATCH bpf-next v7 4/9] bpf: Add syscall common attributes support " Leon Hwang
2026-01-23 3:24 ` [PATCH bpf-next v7 5/9] bpf: Refactor reporting btf_log_true_size for btf_load Leon Hwang
2026-01-23 3:24 ` [PATCH bpf-next v7 6/9] bpf: Add syscall common attributes support " Leon Hwang
2026-01-23 3:24 ` [PATCH bpf-next v7 7/9] bpf: Add syscall common attributes support for map_create Leon Hwang
2026-01-23 3:24 ` [PATCH bpf-next v7 8/9] libbpf: Add common attr " Leon Hwang
2026-01-23 3:24 ` [PATCH bpf-next v7 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=a0ce1dab-7d7e-4b04-a033-4f0611090d34@linux.dev \
--to=leon.hwang@linux.dev \
--cc=a.s.protopopov@gmail.com \
--cc=aalbersh@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ameryhung@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.