intent: follow 7.2 rename RANDOM_KMALLOC_CACHES -> KMALLOC_PARTITION_CACHES #57
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-kmalloc-partition-rename"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes the failed
v7.2.5-hardened1build (run 3016): the fidelity assertion reportedMISS CONFIG_RANDOM_KMALLOC_CACHES: want =y, got <absent>.Cause. Upstream 7.2 renamed
RANDOM_KMALLOC_CACHES→KMALLOC_PARTITION_CACHESand split it into a mode choice (KMALLOC_PARTITION_RANDOM, the former behaviour, orKMALLOC_PARTITION_TYPEDvia Clang ≥ 22 alloc tokens). The old symbol is a promptless transitional stub, soolddefconfigdropped our pin.Fix.
configs/intent.config: pinKMALLOC_PARTITION_CACHES=yandKMALLOC_PARTITION_RANDOM=y. The mode is pinned explicitly because the choice defaults to TYPED whenever the compiler advertises alloc-token support; we build with GCC and a toolchain change should not flip a hardening mode unreviewed. Matches anthraxx 7.2.5.hardened1-1.configs/POLICY.md: entry renamed, rename explained. Parity check passes locally.Why the seed-bump PR said "no hardening-relevant changes".
tools/bump-seed.sh's delta filter applies theHARDENregex (anchored at line start for bare.configlines) todiff -uoutput, whose lines start with+/-. It could never match, so every seed-bump PR ever opened reported no hardening changes, including #55's 7.1 → 7.2 jump. Fixed inbump-seed.shandreconcile-vs-anthraxx.shby matching through the diff marker. On the real 7.1.9 → 7.2.5 seed diff the filter now prints exactly:check-hardening-drift.shfeeds bare lines and was unaffected.KMALLOC_PARTITION|RANDOM_KMALLOCadded to theHARDENprefix set in all three scripts.After merging: delete and re-cut
v7.2.5-hardened1(the tag push is the only build trigger). Independent of #56.🤖 Generated with Claude Code
The first v7.2.5-hardened1 build (run 3016) failed the fidelity assertion: MISS CONFIG_RANDOM_KMALLOC_CACHES: want =y, got <absent> Upstream 7.2 renamed RANDOM_KMALLOC_CACHES to KMALLOC_PARTITION_CACHES and split the mechanism into a mode choice (KMALLOC_PARTITION_RANDOM, the former behaviour, or KMALLOC_PARTITION_TYPED via Clang >= 22 alloc tokens); the old symbol is now a promptless transitional stub, so olddefconfig dropped it. - configs/intent.config: pin KMALLOC_PARTITION_CACHES=y and KMALLOC_PARTITION_RANDOM=y. The mode is pinned explicitly because the choice defaults to TYPED whenever the compiler advertises alloc-token support; we build with GCC, and a toolchain change should not flip a hardening mode unreviewed. Matches anthraxx 7.2.5.hardened1-1. - configs/POLICY.md: entry renamed and the rename explained. Why nobody saw it coming: tools/bump-seed.sh's "kconfig delta (hardening-relevant only)" filter applies HARDEN -- a regex anchored at line start for bare .config lines -- to `diff -u` output, whose lines begin with +/-. It could never match, so every seed-bump PR (including #55's 7.1 -> 7.2 jump) reported "no hardening-relevant changes". Fixed in bump-seed.sh and reconcile-vs-anthraxx.sh by matching through the diff marker; on the real 7.1.9 -> 7.2.5 seed diff the filter now prints exactly the three lines above. check-hardening-drift.sh feeds bare lines and was unaffected. KMALLOC_PARTITION|RANDOM_KMALLOC added to the HARDEN prefix set in all three scripts. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>