From: patchwork-bot+netdevbpf@kernel.org
To: Mingpei CAO <caomingpei@gmail.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, eddyz87@gmail.com,
ameryhung@gmail.com
Subject: Re: [PATCH bpf v3 0/2] libbpf: Reject local struct_ops bitfields before data access
Date: Thu, 17 Sep 2026 22:30:08 +0000 [thread overview]
Message-ID: <178968420812.152767.15748849825891235642.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260915162252.473044-1-caomingpei@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 15 Sep 2026 16:22:35 +0000 you wrote:
> A local struct_ops type can contain a bitfield absent from the
> corresponding kernel BTF type. libbpf calculated the member data pointer
> from the encoded BTF member offset before rejecting the bitfield. The
> absent member zero check could then read outside the local struct_ops data
> and crash libbpf.
>
> Patch 1 rejects local bitfields before calculating the member data pointer.
> Patch 2 adds a negative test for a local bitfield absent from the kernel
> BTF type.
>
> [...]
Here is the summary with links:
- [bpf,v3,1/2] libbpf: Reject local struct_ops bitfields before data access
https://git.kernel.org/bpf/bpf-next/c/961b8946acb4
- [bpf,v3,2/2] selftests/bpf: Test local struct_ops bitfield rejection
(no matching commit)
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-09-17 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 16:22 [PATCH bpf v3 0/2] libbpf: Reject local struct_ops bitfields before data access Mingpei CAO
2026-09-15 16:22 ` [PATCH bpf v3 1/2] " Mingpei CAO
2026-09-15 17:40 ` Amery Hung
2026-09-15 16:22 ` [PATCH bpf v3 2/2] selftests/bpf: Test local struct_ops bitfield rejection Mingpei CAO
2026-09-15 17:30 ` bot+bpf-ci
2026-09-17 22:30 ` 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=178968420812.152767.15748849825891235642.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=caomingpei@gmail.com \
--cc=eddyz87@gmail.com \
/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.