Checkpoint owned snapshot components and repair mounted shutdown - #126
Merged
Conversation
9 tasks
yifanxuaaa
changed the title
yifanxuaaa
marked this pull request as ready for review
September 14, 2026 01:07
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
1 participant
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.
This checkpoint adds the host-owned overlay/snapshot components and fixes the mounted host client holding its mount-root descriptor through unmount. The owner explicitly requested stopping after the three current integration fixes, publishing the accumulated checkpoint to main, and leaving a successor handoff.
The three bounded fixes are verified: the real mounted SDK/descriptor/namespace/C1/C2 check now passes through normal unmount and owner-container cleanup; deterministic varied input makes the capacity fixture perform real spill and pass its unchanged ownership assertions; the maintenance oracle now proves a real retained canonical stage before checking deferral. Original failures and unaffected pass reuse are preserved. Independent review found no new blocker in these scoped fixes.
Validation: Rust1.85.1 workspace build, formatting/whitespace and7 runner tests pass. The full native gate reported611 passes and26 ignored across637 selections,37 binaries and79 batches. Its171s duration failed the then150s ceiling; the owner subsequently accepted171s and authorized180s, now implemented. Historical125s/120s and171s/150s failures are retained. Strict Clippy still fails on unused/dead code and style/integration findings; this is an explicitly unfinished checkpoint, not clean CI or feature acceptance.
The public default Workspace mount/Commit route still uses the legacy integration. Generic dirty-mmap snapshot acquisition (V1), remaining ownership/capacity/public lifecycle work, final qualification and the full non-#122 benchmark campaign remain open. The mounted component test supplies owned input explicitly and does not establish generic kernel acquisition. No issue is automatically closed, and no release/tag is included.
Product/evidence source: f8ed6bb. Current CI budget commit:820ecab8079c7e0f09c29c6df1c983366e3dd77e.
Successor handoff: https://github.com/Ephemeral-AI-Lab/layerfs/blob/820ecab8079c7e0f09c29c6df1c983366e3dd77e/docs/roadmap/0.1/0.1.6/overlay-snapshot-step1-handoff.md
Mounted PASS: https://github.com/Ephemeral-AI-Lab/layerfs/blob/f8ed6bbbb3cc86eea23b82d3efa96c70b0519d2a/docs/roadmap/0.1/0.1.6/evidence/phase3-host-operations/mounted-host-attempt02.json
Full checkpoint results/raw logs: https://github.com/Ephemeral-AI-Lab/layerfs/tree/f8ed6bbbb3cc86eea23b82d3efa96c70b0519d2a/docs/roadmap/0.1/0.1.6/evidence/step1-publication
Keep implementation issue#124 and benchmark issue#125 open. All36 exact#122 scenarios remain excluded; no final benchmark campaign ran.