arm64-attach: parity probe compiled-in defaults without lsphp -n (prints usage); allow the one known upload_progress default

Run 5816 built cac-lsphp:php85 arm64 fine (ext-build fix, cac_path_parity 10/10) and the effective
parity matched (62/62 extensions, 351/351 ini values) but the `-n` probe only printed lsphp's usage.
Use PHP_INI_SCAN_DIR=/nonexistent + -c /nonexistent for the compiled-in defaults. Measured: the
packaged arm64 lsphp is compiled with session.upload_progress.enabled=0, amd64 with 1; the shipped
ini sets 0 on both, so the effective value is identical. Only that directive may differ.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0185ukXi4YX5FxJGqhi6qab6
This commit is contained in:
shadowdaoandClaude Sonnet 5.5 committed 2026-11-20 07:57:03 -08:00
1 parent 2c7a04b4d0
commit d7141a5e1a
2 files changed
+36 -10

No files matched your search

+15 -2
View File
@@ -21,9 +21,22 @@ apt, noble arm64), not from source, because:
* the result is checked, not assumed: the workflow runs `scripts/arm64-parity-probe.php` natively in
the existing amd64 image and under QEMU in the new arm64 image and FAILS the run (tag untouched)
on any difference in PHP_VERSION, SAPI, the loaded extension list and versions, or any of the
~350 ini values (with the image's config and with `-n`). It also compares the OpenLiteSpeed
~350 ini values, with the image's own config (what customers get) and with no ini at all
(compiled-in defaults; one known exception below). It also compares the OpenLiteSpeed
version and module versions (LiteSpeed's per-arch "BUILD built:" stamp is ignored).
Measured 2026-11-20 on cac-lsphp:php85: 418 lines identical.
Measured 2026-11-20 on cac-lsphp:php85: 62/62 extensions and 351/351 effective ini values identical.
### Known difference: compiled-in `session.upload_progress.enabled`
LiteSpeed's packaged arm64 lsphp is compiled with `session.upload_progress.enabled=0`; its amd64
package reports `1`, and our php.net-source amd64 images copy that `1` on purpose
(`lsphp-src-build.sh` step 2c). Both architectures ship `session.upload_progress.enabled = 0` in
`zz-php2shell-mitigation.ini`, so the EFFECTIVE value is `0` on both (`php -i` in a running
container, the `cfg` probe, which the gate compares with no exception). Only the compiled-in
default (visible with no ini files, e.g. `PHP_INI_SCAN_DIR=/nonexistent lsphp -c /nonexistent`)
differs, and the gate allows exactly that one directive. If identical compiled-in defaults are ever
required, the arm64 image would have to be built from php.net source (the source path would need
its step 2c to accept a packaged default of `0`; not done).
`EXPECT_LSPHP_PKG` / `EXPECT_PHP_VERSION` come from the arm64 repo index
(`scripts/lsphp-repo-version.sh PHPVER arm64`), not the amd64 one.