From: sashiko-bot@kernel.org
To: "Leon Hwang" <leon.hwang@linux.dev>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v14 7/8] libbpf: Add syscall common attributes support for map_create
Date: Thu, 14 May 2026 01:08:49 +0000 [thread overview]
Message-ID: <20260514010850.0F569C19425@smtp.kernel.org> (raw)
In-Reply-To: <20260512153157.28382-8-leon.hwang@linux.dev>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing OPTS_VALID() check for the nested `log_opts` structure in `bpf_map_create` breaks ABI forward compatibility guarantees.
--
commit a5ab21cbf48e1fc2cdb0af0f1ff743e2633f6ae8
Author: Leon Hwang <leon.hwang@linux.dev>
libbpf: Add syscall common attributes support for map_create
The commit introduces struct bpf_log_opts and adds a log_opts field to
bpf_map_create_opts to allow users to retrieve detailed error messages when
map creation fails.
> diff --git a/tools/lib/bpf/bpf.c b/tools/lib/bpf/bpf.c
> index 9d8740761b7a8..483c02cf21d1f 100644
> --- a/tools/lib/bpf/bpf.c
> +++ b/tools/lib/bpf/bpf.c
[ ... ]
> @@ -242,7 +245,18 @@ 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);
> + log_opts = OPTS_GET(opts, log_opts, NULL);
Does this code need to validate log_opts with OPTS_VALID(log_opts, bpf_log_opts)?
Libbpf relies on the OPTS_VALID() macro to enforce ABI forward compatibility
by verifying that any unrecognized trailing fields in extended option structs
are explicitly zeroed. While bpf_map_create() correctly validates the outer
bpf_map_create_opts structure, it seems the nested log_opts structure is
accessed without similar validation.
If a newer application populates unsupported fields in struct bpf_log_opts
with non-zero values, could an older libbpf silently ignore them instead of
safely rejecting the request with -EINVAL?
> + if (log_opts && feat_supported(NULL, FEAT_BPF_SYSCALL_COMMON_ATTRS)) {
> + memset(&attr_common, 0, attr_common_sz);
> + attr_common.log_buf = ptr_to_u64(OPTS_GET(log_opts, buf, NULL));
> + attr_common.log_size = OPTS_GET(log_opts, size, 0);
> + attr_common.log_level = OPTS_GET(log_opts, level, 0);
> + fd = sys_bpf_ext_fd(BPF_MAP_CREATE, &attr, attr_sz, &attr_common, attr_common_sz);
> + OPTS_SET(log_opts, true_size, attr_common.log_true_size);
> + } else {
> + fd = sys_bpf_fd(BPF_MAP_CREATE, &attr, attr_sz);
> + OPTS_SET(log_opts, true_size, 0);
> + }
> return libbpf_err_errno(fd);
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260512153157.28382-1-leon.hwang@linux.dev?part=7
next prev parent reply other threads:[~2026-05-14 1:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 15:31 [PATCH bpf-next v14 0/8] bpf: Extend BPF syscall with common attributes support Leon Hwang
2026-05-12 15:31 ` [PATCH bpf-next v14 1/8] " Leon Hwang
2026-05-13 22:48 ` sashiko-bot
2026-05-12 15:31 ` [PATCH bpf-next v14 2/8] libbpf: Add support for extended BPF syscall Leon Hwang
2026-05-12 16:23 ` bot+bpf-ci
2026-05-13 2:10 ` Leon Hwang
2026-05-12 15:31 ` [PATCH bpf-next v14 3/8] bpf: Refactor reporting log_true_size for prog_load Leon Hwang
2026-05-12 15:31 ` [PATCH bpf-next v14 4/8] bpf: Add syscall common attributes support " Leon Hwang
2026-05-13 23:56 ` sashiko-bot
2026-05-12 15:31 ` [PATCH bpf-next v14 5/8] bpf: Add syscall common attributes support for btf_load Leon Hwang
2026-05-12 15:31 ` [PATCH bpf-next v14 6/8] bpf: Add syscall common attributes support for map_create Leon Hwang
2026-05-14 0:46 ` sashiko-bot
2026-05-12 15:31 ` [PATCH bpf-next v14 7/8] libbpf: " Leon Hwang
2026-05-14 1:08 ` sashiko-bot [this message]
2026-05-12 15:31 ` [PATCH bpf-next v14 8/8] selftests/bpf: Add tests to verify map create failure log Leon Hwang
2026-05-14 1:25 ` sashiko-bot
2026-05-12 19:50 ` [PATCH bpf-next v14 0/8] bpf: Extend BPF syscall with common attributes support 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=20260514010850.0F569C19425@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=leon.hwang@linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
/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