[BUG] Required completion markers use a retired logging route #8

Closed
opened 2026-10-15 06:24:46 +02:00 by erikinkinen · 4 comments
Owner

Summary

Required completion records must survive retirement of direct diagnostic logging. The ACL metadata verifier still sends its required witness through the retired trace route.

Reproduction

At Integration 104fdec3a5cae54c582c7bbb110052dbc1e04a6d, run:

./scripts/run-scenario.sh tests/scenarios/subsystem-ext4-acl-metadata-positive.toml components.toml

Keep normal Logd bootstrap and direct-kernel authority retirement. The original full CI run reproduces the failure once.

Expected and actual behavior

Successful ACL verification should publish ERIX_ROOTD:TRACE:VFS:ACL_META_OK through the existing authenticated Logd submission. The guest reaches READY, but the scenario fails because that required marker is absent. The verifier calls VfsIoEffects::trace, which forwards through vfs_debug and stops emitting after direct logging is retired. The separate EXT_META completion record remains visible.

Environment and identity

Executing Integration 104fdec3a5cae54c582c7bbb110052dbc1e04a6d; Rootd b2933983368b69b822bb66a64e7eb9613f8510e5; orchestration library selected from Integration 7769fb520cd95da1d32d28077033f5c8fa8cc7b7. The case selects the Rust release profile, development storage configuration, writable ext4 ACL media and one VM CPU.

Evidence and prior checks

Original full VM run. Its log records the ACL feature selection, the missing-marker error and the guest reaching READY. Source review identifies the suppressed diagnostic route. Timed and extended-VFS completion already use checked live submission; the ACL witness needs the same treatment. No logging authority should be restored.

Tracking

Phase completion.

  • Route required Timed and extended-VFS completion records through borrowed live submission authority after successful verification.
  • Cover verifier failure, marker failure, and retired-debug/live-route behavior after direct logging is retired.
  • Keep authority retirement and the existing guest scenarios unchanged.
  • Route the ACL metadata completion witness through the same checked live submission boundary.
  • Confirm the affected original guest scenarios on the repaired coherent graph.
## Summary Required completion records must survive retirement of direct diagnostic logging. The ACL metadata verifier still sends its required witness through the retired trace route. ## Reproduction At Integration `104fdec3a5cae54c582c7bbb110052dbc1e04a6d`, run: ```sh ./scripts/run-scenario.sh tests/scenarios/subsystem-ext4-acl-metadata-positive.toml components.toml ``` Keep normal Logd bootstrap and direct-kernel authority retirement. The original full CI run reproduces the failure once. ## Expected and actual behavior Successful ACL verification should publish `ERIX_ROOTD:TRACE:VFS:ACL_META_OK` through the existing authenticated Logd submission. The guest reaches READY, but the scenario fails because that required marker is absent. The verifier calls `VfsIoEffects::trace`, which forwards through `vfs_debug` and stops emitting after direct logging is retired. The separate EXT_META completion record remains visible. ## Environment and identity Executing Integration `104fdec3a5cae54c582c7bbb110052dbc1e04a6d`; Rootd `b2933983368b69b822bb66a64e7eb9613f8510e5`; orchestration library selected from Integration `7769fb520cd95da1d32d28077033f5c8fa8cc7b7`. The case selects the Rust release profile, development storage configuration, writable ext4 ACL media and one VM CPU. ## Evidence and prior checks [Original full VM run](https://git.erikinkinen.fi/erix/integration/actions/runs/2684). Its log records the ACL feature selection, the missing-marker error and the guest reaching READY. Source review identifies the suppressed diagnostic route. Timed and extended-VFS completion already use checked live submission; the ACL witness needs the same treatment. No logging authority should be restored. ## Tracking [Phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). - [x] Route required Timed and extended-VFS completion records through borrowed live submission authority after successful verification. - [x] Cover verifier failure, marker failure, and retired-debug/live-route behavior after direct logging is retired. - [x] Keep authority retirement and the existing guest scenarios unchanged. - [x] Route the ACL metadata completion witness through the same checked live submission boundary. - [x] Confirm the affected original guest scenarios on the repaired coherent graph.
Author
Owner

The fix is in 5588d9d6. Timed and extended-VFS completion records now use the existing borrowed Logd submission route after the complete verifier and cleanup succeed. A submission error stops later records and pipeline work; direct-kernel diagnostics stay retired.

Catalog adoption and confirmation of the affected guest scenarios remain open in Rootd #8.

The fix is in [`5588d9d6`](https://git.erikinkinen.fi/erix/rootd/commit/5588d9d6f3bac65fbcf6e3f98cf336e1590bdddb). Timed and extended-VFS completion records now use the existing borrowed Logd submission route after the complete verifier and cleanup succeed. A submission error stops later records and pipeline work; direct-kernel diagnostics stay retired. Catalog adoption and confirmation of the affected guest scenarios remain open in [Rootd #8](https://git.erikinkinen.fi/erix/rootd/issues/8).
Author
Owner

The catalog now selects the completion-logging fix in Integration e5c0a7ff. The affected Timed and extended-VFS guest cases remain open.

The catalog now selects the completion-logging fix in [Integration e5c0a7ff](https://git.erikinkinen.fi/erix/integration/commit/e5c0a7ffe59c2c5f94730f5545e0bdf14f402469). The affected Timed and extended-VFS guest cases remain open.
Author
Owner

Published 635892a8: ACL completion now uses the existing authenticated Logd submission owner. Rootd checks that owner before verification and sends the witness only after the verifier succeeds; verifier and terminal submission errors stop the pipeline. The original ACL guest still needs confirmation on the updated component graph.

Published `635892a8`: ACL completion now uses the existing authenticated Logd submission owner. Rootd checks that owner before verification and sends the witness only after the verifier succeeds; verifier and terminal submission errors stop the pipeline. The original ACL guest still needs confirmation on the updated component graph.
Author
Owner

The unchanged ext4 ACL metadata scenario passes with Rootd 635892a8, runtime Integration 975a2e3c and executing Integration 2ca69879. Both required completion records reach live Logd, and the original disk/filesystem checks pass. Direct diagnostic logging authority remains retired. This completes the remaining ACL criterion; earlier Timed and extended-VFS results remain separately recorded.

The unchanged ext4 ACL metadata scenario passes with Rootd `635892a8`, runtime Integration `975a2e3c` and executing Integration `2ca69879`. Both required completion records reach live Logd, and the original disk/filesystem checks pass. Direct diagnostic logging authority remains retired. This completes the remaining ACL criterion; earlier Timed and extended-VFS results remain separately recorded.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:12 +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/rootd#8
No description provided.