[BUG] Required completion markers use a retired logging route #8
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/rootd#8
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
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: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_OKthrough the existing authenticated Logd submission. The guest reaches READY, but the scenario fails because that required marker is absent. The verifier callsVfsIoEffects::trace, which forwards throughvfs_debugand stops emitting after direct logging is retired. The separate EXT_META completion record remains visible.Environment and identity
Executing Integration
104fdec3a5cae54c582c7bbb110052dbc1e04a6d; Rootdb2933983368b69b822bb66a64e7eb9613f8510e5; orchestration library selected from Integration7769fb520cd95da1d32d28077033f5c8fa8cc7b7. 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.
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 catalog now selects the completion-logging fix in Integration e5c0a7ff. The affected Timed and extended-VFS guest cases remain open.
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.The unchanged ext4 ACL metadata scenario passes with Rootd
635892a8, runtime Integration975a2e3cand executing Integration2ca69879. 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.