Repository navigation
Reject stale errno in native datagram confinement proof - #84
Merged
Merged
Conversation
This was referenced Oct 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The native datagram proof could classify a zero or short send as a permission refusal by reading stale errno after collapsing the return value to a boolean. Preserve the raw return and capture errno only after an actual -1 failure; require an attempted send plus -1/EACCES or -1/EPERM before counting refusal. Retain nullable raw-result diagnostics and preserve setup errors through cleanup.
Compile the shared send/result helpers in a deterministic fault-injection regression. Cover zero/short returns with stale errno, genuine permission failures, unknown errors, setup-before-send and first-failure preservation. A copied header with the old guards must execute and fail the named zero/stale-EPERM assertion. This verifier test is separate from the unchanged nine-row real IPC matrix, including concurrent host/private alias replacement; it cannot substitute for native acceptance.
The original Intel job at 3f7067d passed its nine primary IPC rows and correctly rejected the injected zero send, but its legacy comparison hit a separate real -1/EINVAL at an earlier unmodified row. Retain that failed source-bound evidence. The deterministic comparison removes that unrelated-race dependency; the native race cause remains unresolved, unknown errors still fail, and nothing is retried or reclassified for acceptance.
Validation at 62a3068:
This continues the single native admission workstream. Production native integration, Linux support/design review and parent acceptance tasks remain open.
Retained corrected native reports and verification bindings: source-bound evidence. They are retained on the upcoming Windows acceptance branch so recording evidence did not restart this head’s CI. The evidence commit changes no native or Rust implementation.