[BUG] Release arena descriptor shares a writable dynamic-link page #8
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/posixd#8
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Summary
The in-progress Posixd release executable cannot pass the new immutable arena-layout admission check: its read-only descriptor shares a native page with writable dynamic-link metadata. Strict compilation succeeds, but Loaderd correctly rejects the resulting geometry. This artifact has not been accepted for native realm execution.
Reproduction
Build the native release profile with the maintained
linker.ldusing Rust 1.97.1:cargo build --locked --offline --release --all-features --bin posixd --target x86_64-unknown-none. Inspect the resulting ELF's load ranges and the compiledERIXPXSCAPLAY001table. The observed artifact SHA-256 is4ca38c4ae2c2fec64d12ded93b8fd06263c00b04f1f04afdc729956ae285b349.The descriptor begins at virtual address
0x68014000. Read-only.rodataends at0x68014360; writable orphan.dynamicstarts there and.gotfollows at0x68014440. They therefore share the same 4-KiB page. A debug artifact has a separate descriptor page and passes this check; it cannot substitute for release validation.Expected and actual behavior
Expected: the complete compiled descriptor occupies file-backed read-only, nonexecutable pages in every supported native profile.
Actual: the release page's combined load flags are 6 (read/write), despite the descriptor's own segment flags being 4 (read-only). Aligning the later
.dataoutput section does not constrain the earlier writable orphan sections. The admission check refuses this artifact as required.Environment and identity
feature/posix-compat, based on signed5f54a55a5f189559352c7d0e6a2af55aaa37c44f.Evidence and prior checks
The complete four-configuration component matrix passes 51 tests per configuration, strict host/native Clippy, warning-denied builds and rustdoc. Independent ELF inspection then found the release-only page conflict. Original artifacts and permission evidence are retained. Signed correction
5af6cf57bad1b9de94ea9bb1acca879ca0c092d1pads the end of.rodatato a page boundary. Fresh native debug/release builds each contain exactly one complete descriptor on exclusively read-only, nonexecutable pages. Their SHA-256 values are1d84d6b3e9a47ba981e0e6eab43e7ef652e6943d7d71d75cf931aa20a0cc0ad0ande4988ec1c04f664177cd017546bea12e0d1c201f0f42b85ee15b0e7ac5e922c2. The full51-tests-per-configuration matrix is reused only after independent source comparison established the linker script as its sole changed input. Original CI stopped before compilation on the separately tracked helper catalog omission. The corrected workflow’s original CI29/30 now passes at signeda6107525224e9592bb2059bc14659a62d4e4ff1f, whose Rust/dependency/linker inputs remain identical to the corrected consumer. Both native profiles and complete original logs are reviewed without warnings. This closes the descriptor-page defect; coordinated native realm adoption remains separately required.Tracking
Related: Posixd implementation, realm lifecycle, Loaderd layout binding, and phase completion. Keep the release and debug layout checks separate and retain this refused artifact's evidence.
erikinkinen referenced this issue2026-09-24 23:11:11 +02:00