[PATCH bpf-next] bpf/veristat: Fix veristat for map type BPF_MAP_TYPE_CGRP_STORAGE

[PATCH bpf-next] bpf/veristat: Fix veristat for map type BPF_MAP_TYPE_CGRP_STORAGE

[Song Liu]

BPF_MAP_TYPE_CGRP_STORAGE doesn't allow non-zero max_entries. So veristat
should not set it to 1.

Signed-off-by: Song Liu <song@kernel.org>
---
 tools/testing/selftests/bpf/veristat.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tools/testing/selftests/bpf/veristat.c b/tools/testing/selftests/bpf/veristat.c
index b2bb20b00952..70cdabd88c50 100644
--- a/tools/testing/selftests/bpf/veristat.c
+++ b/tools/testing/selftests/bpf/veristat.c
@@ -1182,6 +1182,7 @@ static void fixup_obj(struct bpf_object *obj, struct bpf_program *prog, const ch
 		case BPF_MAP_TYPE_TASK_STORAGE:
 		case BPF_MAP_TYPE_INODE_STORAGE:
 		case BPF_MAP_TYPE_CGROUP_STORAGE:
+		case BPF_MAP_TYPE_CGRP_STORAGE:
 			break;
 		case BPF_MAP_TYPE_STRUCT_OPS:
 			mask_unrelated_struct_ops_progs(obj, map, prog);
-- 
2.47.1

Re: [PATCH bpf-next] bpf/veristat: Fix veristat for map type BPF_MAP_TYPE_CGRP_STORAGE

[patchwork-bot+netdevbpf]

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Thu, 12 Jun 2025 22:00:01 -0700 you wrote:
> BPF_MAP_TYPE_CGRP_STORAGE doesn't allow non-zero max_entries. So veristat
> should not set it to 1.
> 
> Signed-off-by: Song Liu <song@kernel.org>
> ---
>  tools/testing/selftests/bpf/veristat.c | 1 +
>  1 file changed, 1 insertion(+)

Here is the summary with links:
  - [bpf-next] bpf/veristat: Fix veristat for map type BPF_MAP_TYPE_CGRP_STORAGE
    https://git.kernel.org/bpf/bpf-next/c/ccefa19335a0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html