From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf@vger.kernel.org, yonghong.song@linux.dev, malin89@huawei.com,
ast@kernel.org
Subject: Re: [PATCH bpf-next 1/2] bpf: Tighten cgroup storage cookie checks for prog arrays
Date: Wed, 10 Jun 2026 23:20:07 +0000 [thread overview]
Message-ID: <178113360740.3670402.3459348998786835007.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260610105539.705887-1-daniel@iogearbox.net>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 10 Jun 2026 12:55:38 +0200 you wrote:
> The fix in commit abad3d0bad72 ("bpf: Fix oob access in cgroup local
> storage") is still incomplete. The prog-array compatibility check
> treats a program with no cgroup storage as compatible with any stored
> storage cookie. This allows a storage-less program to bridge a tail
> call chain between an entry program and a storage-using callee even
> though cgroup local storage at runtime still follows the caller's
> context, that is, A -> B(no storage) -> C(storage) path.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Tighten cgroup storage cookie checks for prog arrays
https://git.kernel.org/bpf/bpf-next/c/10627ddc0167
- [bpf-next,2/2] selftests/bpf: Cover tail-call cgroup storage prog-array checks
https://git.kernel.org/bpf/bpf-next/c/30dee2c176e7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-10 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 10:55 [PATCH bpf-next 1/2] bpf: Tighten cgroup storage cookie checks for prog arrays Daniel Borkmann
2026-06-10 10:55 ` [PATCH bpf-next 2/2] selftests/bpf: Cover tail-call cgroup storage prog-array checks Daniel Borkmann
2026-06-10 20:15 ` Yonghong Song
2026-06-10 20:14 ` [PATCH bpf-next 1/2] bpf: Tighten cgroup storage cookie checks for prog arrays Yonghong Song
2026-06-10 23:20 ` patchwork-bot+netdevbpf [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=178113360740.3670402.3459348998786835007.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=malin89@huawei.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.