From: patchwork-bot+netdevbpf@kernel.org
To: David Vernet <void@manifault.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Load struct_ops map in global_maps_resize test
Date: Thu, 25 Jul 2024 20:40:31 +0000 [thread overview]
Message-ID: <172194003161.20182.11872236874793276327.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240725032214.50676-1-void@manifault.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 24 Jul 2024 22:22:14 -0500 you wrote:
> In prog_tests/test_global_maps_resize.c, we test various use cases for
> resizing global maps. Commit 7244100e0389 ("libbpf: Don't take direct
> pointers into BTF data from st_ops") updated libbpf to not store pointers
> to volatile BTF data, which for some users, was causing a UAF when resizing
> a datasec array.
>
> Let's ensure we have coverage for resizing datasec arrays with struct_ops
> progs by also including a struct_ops map and struct_ops prog in the
> test_global_map_resize skeleton. The map is automatically loaded, so we
> don't need to do anything other than add it to the BPF prog being tested
> to get the coverage.
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Load struct_ops map in global_maps_resize test
https://git.kernel.org/bpf/bpf-next/c/7d30b8aa4fc3
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:[~2024-07-25 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 3:22 [PATCH bpf-next] selftests/bpf: Load struct_ops map in global_maps_resize test David Vernet
2024-07-25 20:40 ` 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=172194003161.20182.11872236874793276327.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@meta.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=void@manifault.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox