From: patchwork-bot+netdevbpf@kernel.org
To: Mahe Tardy <mahe.tardy@gmail.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, eddyz87@gmail.com,
ihor.solodrai@linux.dev, ast@kernel.org, daniel@iogearbox.net,
memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org, emil@etsalapatis.com,
linux-kernel@vger.kernel.org, john.fastabend@gmail.com
Subject: Re: [PATCH bpf] libbpf: Reject excessive program counts in generated loaders
Date: Thu, 29 Oct 2026 16:10:04 +0000 [thread overview]
Message-ID: <179329020430.546068.5250176039827130736.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261028183947.9606-1-mahe.tardy@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 28 Oct 2026 18:39:47 +0000 you wrote:
> An object containing MAX_USED_PROGS+1 (33) programs successfully
> produces a light skeleton that laters fails at load time with -EACCES
> because saving the 33rd FD emits a store at r10 + 0:
>
> *(u32 *)(r10 +0) = r7
> invalid write to stack R10 off=0 size=4
>
> [...]
Here is the summary with links:
- [bpf] libbpf: Reject excessive program counts in generated loaders
https://git.kernel.org/bpf/bpf-next/c/aac5ba0a4d52
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-10-29 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 18:39 [PATCH bpf] libbpf: Reject excessive program counts in generated loaders Mahe Tardy
2026-10-29 16:10 ` patchwork-bot+netdevbpf [this message]
2026-10-29 16:33 ` Alexei Starovoitov
2026-10-29 20:03 ` Mahe Tardy
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=179329020430.546068.5250176039827130736.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahe.tardy@gmail.com \
--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