[BUG] Runtime process-exit traces split terminal diagnostics #55
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/kernel#55
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
Runtime-image process-exit tracing can interrupt terminal diagnostics on COM1. The directory workflow's required permission-denied message is split by Kernel output, causing its unchanged scenario to fail despite reaching the later workflow and exit markers.
Reproduction
At Integration
f467304fc8f99f4b7d6cd7e23a1254d08e510cef, run:One captured execution failed this way. Frequency is unknown.
Expected and actual behavior
The expected
tmp/coreutils-source: permission deniedmust remain intact. The actual serial output placesERIX_KERNEL:PROCESS_EXIT_TCB=0000000000000023immediately aftercat: tmp/coreutils-source; process-exit endpoint/code records follow before: permission denied.The original checker exits 1 for that missing marker. Its required/unique count is zero, and its ordering check fails at the same message. The copy diagnostic and later workflow/exit markers each occur once; no forbidden marker appears.
Environment and identity
Kernel
e463d945, runtime Integration837b00cd, Rootdff0bd1ef, Coreutils78df1388, TTYd56f9cdf2, Exsh8540bcf4. The original release scenario uses x86_64 QEMU/UEFI, one CPU and a writable single-virtio GPT disk. Kernel features include runtime-image, rootd-smoke-test and dev-console; neither integration-runtime-quiet nor process-destroy-trace is selected. The scenario's create/unlink grants are unchanged.Captured post-run writable disk SHA-256:
87b76a87b8e3287972d636c94f623c606ae7e743bcef0b48429af1618988bd1e. No last working revision is established.Evidence and prior checks
The complete 55,804-byte serial capture has SHA-256
679589c3d582f5b02a459dd65da7b39708d10aedf8864666a99705857db4731a. Its original images, source bindings and native artifacts are retained. All host owners retired successfully. Re-evaluating the original marker parser against those bytes confirms the same refusal.Coreutils emits this diagnostic in separate stream writes. The UART provider and Kernel diagnostic path share COM1 without a whole-record transaction. Joining the Coreutils writes alone would not establish atomicity against the independent Kernel writer.
Tracking
Related: directory cleanup failure. That earlier run failed differently; a shared cause is unproved.
Implemented in
68a65a86. Runtime images now require the existing process-destroy trace for the three routine exit values. Explicit tracing, non-runtime smoke behavior, IPC-switch diagnostics, results and fault reporting keep their existing paths.All eight policy combinations pass. CI921 is running. Integration catalog adoption and the unchanged directory regression are next; the issue stays open for that guest result.
Integration now selects the repair in
ab6a8d59. Kernel CI921 passed. The unchanged directory guest remains the final criterion; no new guest result is claimed yet.Fixed in 68a65a86, adopted by Integration ab6a8d59. The unchanged directory scenario now passes, including both intact permission-denied messages and every required, forbidden, unique and ordered marker check. The producer and both capture operations exited successfully with cleanup confirmed. All three criteria are complete.
The earlier service-exit failure remains open; this result does not establish its cause.