Re: [PATCH bpf-next v3 2/3] bpf: Use bpf_core_enum_value for stats in cgroup_iter_memcg

Next message: Sun Jian: "[PATCH v2 0/2] selftests/bpf: fix bpf_cookie failures"
Previous message: Nicolas Schier: "Re: [PATCH] kbuild: Leave objtool binary around with 'make clean'"
In reply to: Hui Zhu: "[PATCH bpf-next v3 2/3] bpf: Use bpf_core_enum_value for stats in cgroup_iter_memcg"
Next in thread: Emil Tsalapatis: "Re: [PATCH bpf-next v3 2/3] bpf: Use bpf_core_enum_value for stats in cgroup_iter_memcg"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: bot+bpf-ci

Date: Sat Feb 28 2026 - 02:43:37 EST

> The change adds runtime enum value resolution for:
> - node_stat_item: NR_ANON_MAPPED, NR_SHMEM, NR_FILE_PAGES,
> NR_FILE_MAPPED
> - memcg_stat_item: MEMCG_KMEM
> - vm_event_item: PGFAULT

The commit message lists "memcg_stat_item: MEMCG_KMEM" but this patch
does not touch MEMCG_KMEM at all. The prior patch in the series
(fa0721ccce66 "selftests/bpf: Remove kmem subtest from
cgroup_iter_memcg") already removed the MEMCG_KMEM usage entirely.

Should this bullet be dropped from the commit message?

---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md

CI run summary: https://github.com/kernel-patches/bpf/actions/runs/22516077164

AI-authorship-score: low
AI-authorship-explanation: The stale MEMCG_KMEM reference left in the commit message after restructuring the series is characteristic of a human forgetting to update text.
issues-found: 1
issue-severity-score: low
issue-severity-explanation: Commit message lists a MEMCG_KMEM change that does not exist in the patch, causing a mismatch between the commit description and the actual diff.