[BUG] Native table custody witness destroys an occupied CSpace #33

Closed
opened 2026-09-23 09:43:43 +02:00 by erikinkinen · 0 comments
Owner

Summary

The new unpublished-table witness tried to destroy its temporary CSpace while two private VSpace capabilities remained installed. The existing empty-CSpace contract refuses that operation. The first native lifetime run failed before the new custody marker and before any CPL3 execution. The correction retires each exact temporary binding through normal object cleanup before destroying the now-empty CSpace.

Reproduction

One original maintained lifetime-scenario execution selected signed Kernel 7f8d1e4b4a0497a0d68a96d780bd63b46be1b6b1 through Integration 226324940b5101a839c5f392682be48357a620b1. It reached LIFETIME_REVOCATION_BEGIN then LIFETIME_REVOCATION_FAIL; the wrapper exited 1 and QEMU exited 37 instead of 33. The original serial report does not expose the inner Kernel error. Source review and deterministic host controls establish that the final occupied-CSpace destruction necessarily returns CspaceSlotOccupied. No unchanged VM retry was performed.

Seven original principal image/log files and 151 original producer/cache artifacts are preserved. All 15 source signatures verify; the packaged Kernel matches exactly one retained original ELF after normal stripping. This is an actual native diagnostic failure, without a userspace exploit or full guest-build claim.

Expected and actual behavior

The witness must retire its exact temporary VSpace capabilities through the ordinary removal callbacks before destroying their empty CSpace. Original cleanup attempted the latter operation directly. The correction covers empty, partial and complete setup, rejects unexpected capability kinds and preserves unrelated slots. Normal removal retains callback failure and binding rollback behavior; no occupied CSpace storage is discarded to force success.

Environment and identity

Linux x86_64 host, Rust 1.97.1, release Kernel with the lifetime-selftest and dev-console features, explicit TCG, one CPU, OVMF, original 60-second guest deadline and exact signed dependencies. Original BOOT.IMG SHA-256: 34fef2533569f915f916c33e4ec9d7e9b0b9bd1501a47f0f151754d409c8a463. Whole original build/run elapsed 23.401798 seconds; this is not a timing benchmark. Failure occurs before first user entry, with no activatable private root or additional userspace grant.

Evidence and prior checks

Before the original failure, four strict configurations passed 820/844 tests, sixteen native build/Clippy profiles and private rustdoc passed, and all 172 Integration helpers passed. The original image build emitted no warnings, QEMU stderr was empty and process cleanup succeeded. These preparatory checks did not establish native acceptance.

The correction adds three host cleanup controls. Four strict configurations now pass 830/854 tests with three existing ignored cases; all sixteen native build/Clippy profiles and private rustdoc pass without warnings. The corrected catalog preserves every previous witness, grant, image setting and deadline. Six corrected native executions satisfy seven maintained contracts, including the new independence/publication-rollback/disposal witness and ordinary exec-successor across all 73 components. Exact signed sources and retained packaged artifacts verify, with no image warnings or QEMU stderr.

Integration regression acceptance remains open. Process population, readiness, CR3 activation, actual CPU residency, live-root retirement and complete guest rebuilding remain open.

Tracking

Related owned address-space design, Kernel review, Integration review and Phase 6 completion.

Further original ext4 CI evidence — 23 September 2026: Integration 1741 and 1742, at 3c92de7ff68b332adc5d5de41e0e06af7ed4c1fe, complete the 489-scenario catalog with 478/11 and 481/8 pass/fail outcomes. All nineteen failures are ext4 scenarios reaching their original 120-second QEMU deadline, tracked under the existing ext4 deadline report. Rust 320/321-test configurations and Markdown pass. Both corrected managed-frame-occupancy and allocator-domain scenarios pass. The later canonical development/release image and physical-input gates are not reached.

Six complete original Integration logs total 34,342,962 bytes and have verified lengths/hashes with zero warning candidates. With the earlier successful Kernel 660/661 and Docs 1025/1026 logs, fourteen complete logs total 35,963,864 bytes and have zero final warnings. All nineteen timeout transcripts lack VFS_IO readiness and contain no scenario-forbidden fault markers. Eighteen end their complete EriX markers at LOGD_REPLY_WAKE_OK; one metadata transcript ends its complete markers at LOGD_REPLY_WRITE_OK followed by a partial next marker. Printed markers do not identify the executing instruction at the deadline or establish a Logd defect, filesystem cause or host-load explanation.

These are original executions on a later source graph, without retries, wider deadlines or changed success oracles. The ext4 report remains open. Complete corrected CI acceptance for Kernel #33 and Kernel #34 also remains open; passing selected allocator cases does not stand in for unreached workflow gates. This terminal run pair is fully retained and classified. Newer private mapping population checks and their CI remain separate, and full external-toolchain/runtime and EriX guest rebuilding are still required.

Complete owned-traversal CI review — 23 September 2026: original Integration 1743 and 1744, at 4fce71efe6277332b7dcad110c9c87eb57040e58 selecting Kernel b90a80c94721f99d2a829117dd29123b3aaebc7c, both pass all 489 catalog VM scenarios. Native lifetime, managed-frame occupancy, allocator-domain, canonical development/release images, physical input and remaining workflow gates pass. Rust 320/321-test configurations, profiler validation and Markdown also pass. Six complete Integration logs total 26,973,962 bytes with zero warning candidates; with eight previously reviewed Kernel/Docs logs, fourteen complete logs total 28,603,130 bytes with zero final warnings.

This graph retains the exact corrected reserved-heap and temporary-CSpace cleanup code, and its Kernel descends from their signed correction. Complete corrected CI now closes Kernel #33 and Kernel #34. Their original native/host failures and later nineteen ext4 CI deadlines remain retained. No failing job was rerun and no limit or success oracle changed. Both new full runs pass the ext4 scenarios; the original timeout cause is still unproven, so Integration #73 remains open for attribution and timing review.

Later leaf/population/ancestor cohorts retain their own CI acceptance. Complete semantic authority review, root activation, external Rust/LLVM/runtime rebuilding and both complete EriX guest-build generations remain required. Canonical acceptance stays 15/460 leaves, weighted 3.48%.

## Summary The new unpublished-table witness tried to destroy its temporary CSpace while two private VSpace capabilities remained installed. The existing empty-CSpace contract refuses that operation. The first native lifetime run failed before the new custody marker and before any CPL3 execution. The [correction](https://git.erikinkinen.fi/erix/kernel/commit/03f3412076a9dde92ad4e89902d5ec8497a08476) retires each exact temporary binding through normal object cleanup before destroying the now-empty CSpace. ## Reproduction One original maintained lifetime-scenario execution selected signed Kernel `7f8d1e4b4a0497a0d68a96d780bd63b46be1b6b1` through Integration `226324940b5101a839c5f392682be48357a620b1`. It reached LIFETIME_REVOCATION_BEGIN then LIFETIME_REVOCATION_FAIL; the wrapper exited 1 and QEMU exited 37 instead of 33. The original serial report does not expose the inner Kernel error. Source review and deterministic host controls establish that the final occupied-CSpace destruction necessarily returns CspaceSlotOccupied. No unchanged VM retry was performed. Seven original principal image/log files and 151 original producer/cache artifacts are preserved. All 15 source signatures verify; the packaged Kernel matches exactly one retained original ELF after normal stripping. This is an actual native diagnostic failure, without a userspace exploit or full guest-build claim. ## Expected and actual behavior The witness must retire its exact temporary VSpace capabilities through the ordinary removal callbacks before destroying their empty CSpace. Original cleanup attempted the latter operation directly. The correction covers empty, partial and complete setup, rejects unexpected capability kinds and preserves unrelated slots. Normal removal retains callback failure and binding rollback behavior; no occupied CSpace storage is discarded to force success. ## Environment and identity Linux x86_64 host, Rust 1.97.1, release Kernel with the lifetime-selftest and dev-console features, explicit TCG, one CPU, OVMF, original 60-second guest deadline and exact signed dependencies. Original BOOT.IMG SHA-256: `34fef2533569f915f916c33e4ec9d7e9b0b9bd1501a47f0f151754d409c8a463`. Whole original build/run elapsed 23.401798 seconds; this is not a timing benchmark. Failure occurs before first user entry, with no activatable private root or additional userspace grant. ## Evidence and prior checks Before the original failure, four strict configurations passed 820/844 tests, sixteen native build/Clippy profiles and private rustdoc passed, and all 172 Integration helpers passed. The original image build emitted no warnings, QEMU stderr was empty and process cleanup succeeded. These preparatory checks did not establish native acceptance. The correction adds three host cleanup controls. Four strict configurations now pass 830/854 tests with three existing ignored cases; all sixteen native build/Clippy profiles and private rustdoc pass without warnings. The [corrected catalog](https://git.erikinkinen.fi/erix/integration/commit/634062c06d427c0c8dc0916448a073e50e260adc) preserves every previous witness, grant, image setting and deadline. Six corrected native executions satisfy seven maintained contracts, including the new independence/publication-rollback/disposal witness and ordinary exec-successor across all 73 components. Exact signed sources and retained packaged artifacts verify, with no image warnings or QEMU stderr. Integration regression acceptance remains open. Process population, readiness, CR3 activation, actual CPU residency, live-root retirement and complete guest rebuilding remain open. ## Tracking Related [owned address-space design](https://git.erikinkinen.fi/erix/kernel/issues/22), [Kernel review](https://git.erikinkinen.fi/erix/kernel/pulls/3), [Integration review](https://git.erikinkinen.fi/erix/integration/pulls/12) and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Further original ext4 CI evidence — 23 September 2026: Integration [1741](https://git.erikinkinen.fi/erix/integration/actions/runs/1741) and [1742](https://git.erikinkinen.fi/erix/integration/actions/runs/1742), at `3c92de7ff68b332adc5d5de41e0e06af7ed4c1fe`, complete the 489-scenario catalog with 478/11 and 481/8 pass/fail outcomes. All nineteen failures are ext4 scenarios reaching their original 120-second QEMU deadline, tracked under [the existing ext4 deadline report](https://git.erikinkinen.fi/erix/integration/issues/73). Rust 320/321-test configurations and Markdown pass. Both corrected managed-frame-occupancy and allocator-domain scenarios pass. The later canonical development/release image and physical-input gates are not reached. Six complete original Integration logs total 34,342,962 bytes and have verified lengths/hashes with zero warning candidates. With the earlier successful Kernel 660/661 and Docs 1025/1026 logs, fourteen complete logs total 35,963,864 bytes and have zero final warnings. All nineteen timeout transcripts lack VFS_IO readiness and contain no scenario-forbidden fault markers. Eighteen end their complete EriX markers at LOGD_REPLY_WAKE_OK; one metadata transcript ends its complete markers at LOGD_REPLY_WRITE_OK followed by a partial next marker. Printed markers do not identify the executing instruction at the deadline or establish a Logd defect, filesystem cause or host-load explanation. These are original executions on a later source graph, without retries, wider deadlines or changed success oracles. The ext4 report remains open. Complete corrected CI acceptance for [Kernel #33](https://git.erikinkinen.fi/erix/kernel/issues/33) and [Kernel #34](https://git.erikinkinen.fi/erix/kernel/issues/34) also remains open; passing selected allocator cases does not stand in for unreached workflow gates. This terminal run pair is fully retained and classified. Newer private mapping population checks and their CI remain separate, and full external-toolchain/runtime and EriX guest rebuilding are still required. Complete owned-traversal CI review — 23 September 2026: original Integration [1743](https://git.erikinkinen.fi/erix/integration/actions/runs/1743) and [1744](https://git.erikinkinen.fi/erix/integration/actions/runs/1744), at `4fce71efe6277332b7dcad110c9c87eb57040e58` selecting Kernel `b90a80c94721f99d2a829117dd29123b3aaebc7c`, both pass all 489 catalog VM scenarios. Native lifetime, managed-frame occupancy, allocator-domain, canonical development/release images, physical input and remaining workflow gates pass. Rust 320/321-test configurations, profiler validation and Markdown also pass. Six complete Integration logs total 26,973,962 bytes with zero warning candidates; with eight previously reviewed Kernel/Docs logs, fourteen complete logs total 28,603,130 bytes with zero final warnings. This graph retains the exact corrected reserved-heap and temporary-CSpace cleanup code, and its Kernel descends from their signed correction. Complete corrected CI now closes [Kernel #33](https://git.erikinkinen.fi/erix/kernel/issues/33) and [Kernel #34](https://git.erikinkinen.fi/erix/kernel/issues/34). Their original native/host failures and later nineteen ext4 CI deadlines remain retained. No failing job was rerun and no limit or success oracle changed. Both new full runs pass the ext4 scenarios; the original timeout cause is still unproven, so [Integration #73](https://git.erikinkinen.fi/erix/integration/issues/73) remains open for attribution and timing review. Later leaf/population/ancestor cohorts retain their own CI acceptance. Complete semantic authority review, root activation, external Rust/LLVM/runtime rebuilding and both complete EriX guest-build generations remain required. Canonical acceptance stays 15/460 leaves, weighted 3.48%.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:28 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/kernel#33
No description provided.