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 8/9] libbpf: Add common attr support for map_create
Date: Fri, 16 Jan 2026 22:17:20 +0800 [thread overview]
Message-ID: <22e0de9a-8963-454b-8b35-f8c9be15dee3@linux.dev> (raw)
In-Reply-To: <CAEf4BzarSrW1aTRcjrheLWqxFCh1FFd7vwJ4OQup1dbT13EapQ@mail.gmail.com>
On 2026/1/16 09:03, Andrii Nakryiko wrote:
> On Mon, Jan 12, 2026 at 6:59 AM Leon Hwang <leon.hwang@linux.dev> wrote:
>>
>> With the previous commit adding common attribute support for
>> BPF_MAP_CREATE, users can now retrieve detailed error messages when map
>> creation fails via the log_buf field.
>>
>> Introduce struct bpf_syscall_common_attr_opts with the following fields:
>> log_buf, log_size, log_level, and log_true_size.
>>
>> Extend bpf_map_create_opts with a new field common_attr_opts, allowing
>> users to capture and inspect log messages on map creation failures.
>>
>> Signed-off-by: Leon Hwang <leon.hwang@linux.dev>
>> ---
>> tools/lib/bpf/bpf.c | 15 ++++++++++++++-
>> tools/lib/bpf/bpf.h | 17 ++++++++++++++++-
>> 2 files changed, 30 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/lib/bpf/bpf.c b/tools/lib/bpf/bpf.c
>> index d44e667aaf02..d65df1b7b2be 100644
>> --- a/tools/lib/bpf/bpf.c
>> +++ b/tools/lib/bpf/bpf.c
>> @@ -207,6 +207,9 @@ int bpf_map_create(enum bpf_map_type map_type,
>> const struct bpf_map_create_opts *opts)
>> {
>> const size_t attr_sz = offsetofend(union bpf_attr, excl_prog_hash_size);
>> + const size_t common_attr_sz = sizeof(struct bpf_common_attr);
>> + struct bpf_syscall_common_attr_opts *common_attr_opts;
>> + struct bpf_common_attr common_attr;
>> union bpf_attr attr;
>> int fd;
>>
>> @@ -240,7 +243,17 @@ int bpf_map_create(enum bpf_map_type map_type,
>> attr.excl_prog_hash = ptr_to_u64(OPTS_GET(opts, excl_prog_hash, NULL));
>> attr.excl_prog_hash_size = OPTS_GET(opts, excl_prog_hash_size, 0);
>>
>> - fd = sys_bpf_fd(BPF_MAP_CREATE, &attr, attr_sz);
>> + common_attr_opts = OPTS_GET(opts, common_attr_opts, NULL);
>> + if (common_attr_opts && feat_supported(NULL, FEAT_EXTENDED_SYSCALL)) {
>> + memset(&common_attr, 0, common_attr_sz);
>> + common_attr.log_buf = ptr_to_u64(OPTS_GET(common_attr_opts, log_buf, NULL));
>> + common_attr.log_size = OPTS_GET(common_attr_opts, log_size, 0);
>> + common_attr.log_level = OPTS_GET(common_attr_opts, log_level, 0);
>> + fd = sys_bpf_ext_fd(BPF_MAP_CREATE, &attr, attr_sz, &common_attr, common_attr_sz);
>> + OPTS_SET(common_attr_opts, log_true_size, common_attr.log_true_size);
>> + } else {
>> + fd = sys_bpf_fd(BPF_MAP_CREATE, &attr, attr_sz);
>
> OPTS_SET(log_true_size) to zero here, maybe?
>
Unnecessary, but ok to do it.
>> + }
>> return libbpf_err_errno(fd);
>> }
>>
>> diff --git a/tools/lib/bpf/bpf.h b/tools/lib/bpf/bpf.h
>> index 2c8e88ddb674..c4a26e6b71ea 100644
>> --- a/tools/lib/bpf/bpf.h
>> +++ b/tools/lib/bpf/bpf.h
>> @@ -37,6 +37,18 @@ extern "C" {
>>
>> LIBBPF_API int libbpf_set_memlock_rlim(size_t memlock_bytes);
>>
>> +struct bpf_syscall_common_attr_opts {
>> + size_t sz; /* size of this struct for forward/backward compatibility */
>> +
>> + char *log_buf;
>> + __u32 log_size;
>> + __u32 log_level;
>> + __u32 log_true_size;
>> +
>> + size_t :0;
>> +};
>> +#define bpf_syscall_common_attr_opts__last_field log_true_size
>
> see below, let's drop this struct and just add these 4 fields directly
> to bpf_map_create_opts
>
>> +
>> struct bpf_map_create_opts {
>> size_t sz; /* size of this struct for forward/backward compatibility */
>>
>> @@ -57,9 +69,12 @@ struct bpf_map_create_opts {
>>
>> const void *excl_prog_hash;
>> __u32 excl_prog_hash_size;
>> +
>> + struct bpf_syscall_common_attr_opts *common_attr_opts;
>
> maybe let's just add those log_xxx fields here directly? This whole
> extra bpf_syscall_common_attr_opts pointer and struct seems like a
> cumbersome API.
>
Oops... This struct was suggested by the v3 discussion [1].
This struct was used to report 'log_true_size' without changing
'bpf_map_create()' API.
Links
[1]
https://lore.kernel.org/bpf/CAEf4Bzaw9cboFSf1OXmD84S7pKaeyj=bcQg_diUzGwAkFsjUgg@mail.gmail.com/
Thanks,
Leon
>> +
>> size_t :0;
>> };
>> -#define bpf_map_create_opts__last_field excl_prog_hash_size
>> +#define bpf_map_create_opts__last_field common_attr_opts
>>
>> LIBBPF_API int bpf_map_create(enum bpf_map_type map_type,
>> const char *map_name,
>> --
>> 2.52.0
>>
next prev parent reply other threads:[~2026-01-16 14:17 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
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 [this message]
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=22e0de9a-8963-454b-8b35-f8c9be15dee3@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