generated from erix/meta
[BUG] Preserve the supported minor in malformed I/O fixtures #4
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/lib-posixabi#4
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 malformed-I/O test still expects supported compatibility minor 4 to be rejected, then restores obsolete minor 3 before expecting a successful header parse. Both expectations conflict with the published 1.4 codec. This is a source-observed test regression; no test or CI run was performed.
Reproduction
At revision
7ae4eeedb456d8d02057fab387b0e529df8a4c35, inspectVERSION_MINOR_V1insrc/header.rsandexact_minor_and_declared_large_lengths_are_preservedintests/io_wire_invalid.rs. The codec accepts 4, the rejection list contains 4, and the later successful-header case selects 3.Expected and actual behavior
Expected: accept the independent supported fixture, reject previous/future minors, then restore that same supported fixture before inspecting declared lengths.
Actual in source: stale expectations invert the supported revision and prevent the length case from reaching its intended assertion. During the coordinated compatibility 1.5 change, update rejected revisions, explicitly establish the initial valid fixture, and restore its original minor bytes instead of another disconnected literal.
Environment and identity
feature/posix-compat, starting revision above.Evidence and prior checks
Conditional provider acquisition checkpoint: lib-ipc
bb5df3d2, lib-posixabicdc6eb9e, ramfsdba8ea6da, docsd470ea50, integrationb9acf76b, rootd27835abd.Compatibility 1.5 now describes Open/openat with raw borrowed pathname bytes and checked independent base, access, lookup, shared-status, inheritance and creation-mode domains. Private provider acquisition/retirement framing retains an original root and acquisition identity before submission. Ramfsd compares actual parent permission evidence and pins no-follow files, directories or symlinks in one exclusive turn. Cleanup does not require the original handle reply; retirement fences delayed replay without tombstone storage. Intermediate directory closure preserves independent children, and the original root cannot close while its pins remain.
Eighteen new controls are authored and unrun: five compatibility codecs, five private-provider codecs and eight actual Ramfsd state/dispatch cases. Ramfsd's live-handle helper types and stale compatibility-minor fixture expectations are corrected from source observations. No compiler or test failure is claimed. Component contracts and maintained manual/API-reference source are updated, and Rustfmt was applied.
Full native open/openat remains open: native source preparation, VFS candidate ownership, other providers, Posixd serving, creation/append effects and native workloads are unfinished. No acquisition acceptance credit is added. Weighted completion remains 16.91%, with 21/460 parents and 441/902 sub-items complete. Both EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished.
The exact conflicting constants and assertions are identified above. Preserve independent literal framing and existing malformed-length coverage. Test execution remains deferred by user instruction; authored source controls are not reported as passing.
Tracking
Owning review: #3. Related acquisition work: erix/posixd#17. Phase tracking: erix/integration#65.
erikinkinen referenced this issue from erix/docs2026-09-29 19:19:08 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 19:19:18 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-09-29 19:19:27 +02:00
erikinkinen referenced this issue2026-09-29 19:19:28 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-09-29 19:19:38 +02:00