From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: Luis Vieira <luisflavieira@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
Emil Tsalapatis <emil@etsalapatis.com>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
Shuah Khan <shuah@kernel.org>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf] libbpf: Fix program log buffer size validation
Date: Mon, 14 Sep 2026 14:22:13 +0100 [thread overview]
Message-ID: <05221557-59b5-4d93-ac55-d9e372d0862b@gmail.com> (raw)
In-Reply-To: <20260914-libbpf-log-buf-fix-v1-1-f592caffcc71@gmail.com>
On 9/14/26 12:50 PM, Luis Vieira wrote:
> bpf_program__set_log_buf() intends to reject log buffer sizes larger
> than UINT_MAX.
>
> However, the function checks the existing prog->log_size instead of
> the incoming log_size argument. As a result, an oversized value can
> be accepted.
>
> Validate the supplied log_size instead.
>
> Add a regression test that verifies that values larger than UINT_MAX
> are rejected with -EINVAL on platforms where size_t can represent
> such values.
>
> Fixes: b3ce90795035 ("libbpf: Add per-program log buffer setter and getter")
> Signed-off-by: Luis Vieira <luisflavieira@gmail.com>
> ---
The change looks correct, few questions:
* Do we really need a unit test for this? We are not testing those error
conditions now.
* While here should we rewrite the first check as (!!log_buf != !!log_size), to
cover the case when log_size == 0 but log_buf is nonnull (we check it later in
bpf_prog_load()) (AI)
* Fixes tag is probably not needed, because this is libbpf, target bpf-next.
> tools/lib/bpf/libbpf.c | 2 +-
> tools/testing/selftests/bpf/prog_tests/log_buf.c | 25 ++++++++++++++++++++++++
> 2 files changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> index b749c01742ee..e1fed7735614 100644
> --- a/tools/lib/bpf/libbpf.c
> +++ b/tools/lib/bpf/libbpf.c
> @@ -9955,7 +9955,7 @@ int bpf_program__set_log_buf(struct bpf_program *prog, char *log_buf, size_t log
> {
> if (log_size && !log_buf)
> return libbpf_err(-EINVAL);
> - if (prog->log_size > UINT_MAX)
> + if (log_size > UINT_MAX)
> return libbpf_err(-EINVAL);
> if (prog->obj->state >= OBJ_LOADED)
> return libbpf_err(-EBUSY);
> diff --git a/tools/testing/selftests/bpf/prog_tests/log_buf.c b/tools/testing/selftests/bpf/prog_tests/log_buf.c
> index d6f14a232002..31c842d27fb4 100644
> --- a/tools/testing/selftests/bpf/prog_tests/log_buf.c
> +++ b/tools/testing/selftests/bpf/prog_tests/log_buf.c
> @@ -3,6 +3,8 @@
>
> #include <test_progs.h>
> #include <bpf/btf.h>
> +#include <limits.h>
> +#include <stdint.h>
>
> #include "test_log_buf.skel.h"
> #include "bpf_util.h"
> @@ -267,6 +269,27 @@ static void bpf_btf_load_log_buf(void)
> btf__free(btf);
> }
>
> +static void prog_log_buf_size_limit(void)
> +{
> +#if SIZE_MAX > UINT_MAX
> + struct test_log_buf *skel;
> + char log_buf[1];
> + int err;
> +
> + skel = test_log_buf__open();
> + if (!ASSERT_OK_PTR(skel, "skel_open"))
> + return;
> +
> + err = bpf_program__set_log_buf(skel->progs.good_prog, log_buf,
> + (size_t)UINT_MAX + 1);
> + ASSERT_EQ(err, -EINVAL, "set_log_buf_too_big");
> +
> + test_log_buf__destroy(skel);
> +#else
> + test__skip();
> +#endif
> +}
> +
> void test_log_buf(void)
> {
> if (test__start_subtest("obj_load_log_buf"))
> @@ -275,4 +298,6 @@ void test_log_buf(void)
> bpf_prog_load_log_buf();
> if (test__start_subtest("bpf_btf_load_log_buf"))
> bpf_btf_load_log_buf();
> + if (test__start_subtest("prog_log_buf_size_limit"))
> + prog_log_buf_size_limit();
> }
>
> ---
> base-commit: ee363e055895364039bf28348ff13c615afad4ba
> change-id: 20260913-libbpf-log-buf-fix-49f5038caa5d
>
> Best regards,
> --
> Luis Vieira <luisflavieira@gmail.com>
>
>
next prev parent reply other threads:[~2026-09-14 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 11:50 Luis Vieira
2026-09-14 13:22 ` Mykyta Yatsenko [this message]
2026-09-14 18:25 ` Luís Vieira
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=05221557-59b5-4d93-ac55-d9e372d0862b@gmail.com \
--to=mykyta.yatsenko5@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luisflavieira@gmail.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@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
all inboxes | Powered by JetHome®