From: Mahe Tardy <mahe.tardy@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
Daniel Borkmann <daniel@iogearbox.net>,
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>,
linux-kernel@vger.kernel.org,
John Fastabend <john.fastabend@gmail.com>
Subject: Re: [PATCH bpf] libbpf: Reject excessive program counts in generated loaders
Date: Thu, 29 Oct 2026 21:03:14 +0100 [thread overview]
Message-ID: <auOmggldtZA9AlDV@gmail.com> (raw)
In-Reply-To: <DMHGTWQSAWG9.NUHU0WK9KRK8@gmail.com>
On Thu, Oct 29, 2026 at 04:33:56PM +0000, Alexei Starovoitov wrote:
> On Wed, Oct 28, 2026 at 11:39 AM Mahe Tardy <mahe.tardy@gmail.com> wrote:
> > @@ -122,6 +122,11 @@ void bpf_gen__init(struct bpf_gen *gen, int log_level, int nr_progs, int nr_maps
> > + if (nr_progs > MAX_USED_PROGS) {
> > + pr_warn("Total programs exceeds %d\n", MAX_USED_PROGS);
> > + gen->error = -E2BIG;
> > + return;
> > + }
>
> nr_progs is obj->nr_programs. It counts subprogs and progs with
> autoload == false too. See commit 259172bb6514
> ("libbpf: Fix gen_loader assumption on number of programs.").
> Only a prog that reaches bpf_gen__prog_load() takes a slot in prog_fd[].
>
> Two objects with obj->nr_programs == 33:
>
> object today this patch should be
> ------------------- --------------- ------------- -------------
> 33 progs -EACCES at load -E2BIG at gen -E2BIG at gen
> 1 prog, 32 subprogs -EACCES at load -E2BIG at gen loads
>
> The second object fails today because of the cleanup loop in
> bpf_gen__init(). It closes nr_progs slots of prog_fd[], and
> prog_fd[32] is at r10 + 0:
>
> r1 = *(u32 *)(r10 +0)
> invalid read from stack R10 off=0 size=4
>
> Lets fix both: clamp the loop and check the limit where a prog takes
> the slot, like add_map_fd() does.
> Something like this (not even compile tested):
>
> diff --git a/tools/lib/bpf/gen_loader.c b/tools/lib/bpf/gen_loader.c
> --- a/tools/lib/bpf/gen_loader.c
> +++ b/tools/lib/bpf/gen_loader.c
> @@ -139,6 +139,8 @@ void bpf_gen__init(struct bpf_gen *gen, int log_level, int nr_progs, int nr_maps
> emit(gen, BPF_MOV64_IMM(BPF_REG_3, 0));
> emit(gen, BPF_EMIT_CALL(BPF_FUNC_probe_read_kernel));
>
> + /* nr_progs includes subprogs and progs that are not loaded */
> + nr_progs = min(nr_progs, MAX_USED_PROGS);
> /* amount of stack actually used, only used to calculate iterations, not stack offset */
> nr_progs_sz = offsetof(struct loader_stack, prog_fd[nr_progs]);
> /* jump over cleanup code */
> @@ -1134,6 +1136,11 @@ void bpf_gen__prog_load(struct bpf_gen *gen,
> gen->attach_kind = 0;
> }
> emit_check_err(gen);
> + if (gen->nr_progs == MAX_USED_PROGS) {
> + pr_warn("Total programs exceeds %d\n", MAX_USED_PROGS);
> + gen->error = -E2BIG;
> + return;
> + }
> /* remember prog_fd in the stack, if successful */
> emit(gen, BPF_STX_MEM(BPF_W, BPF_REG_10, BPF_REG_7,
> stack_off(prog_fd[gen->nr_progs])));
>
> since it was already applied. pls send a follow up.
Ah yes this is correct, I bumped into this trying extend the lskel (but
mostly trying to understand their generation for now to be honest) to
allow them to call BPF_LINK_CREATE and somehow I adjusted the nr_progs
passed to bpf_gen__init() earlier to the actual number of progs so I was
not paying attention.
Your patch makes sense to me now and works locally (since
bpf_object__load_progs() is filtering the subprogs and autoload=false we
have at the stage of filling the prog_fd, of course, the correct number
of progs), I tested on an object with 1 prog and 32 subprogs and it's
good now.
I'll send this shortly! Thanks!
prev parent reply other threads:[~2026-10-29 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 18:39 Mahe Tardy
2026-10-29 16:10 ` patchwork-bot+netdevbpf
2026-10-29 16:33 ` Alexei Starovoitov
2026-10-29 20:03 ` Mahe Tardy [this message]
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=auOmggldtZA9AlDV@gmail.com \
--to=mahe.tardy@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@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=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--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®