[BUG] Preserve separate authority and group counts in the binding transcript #11

Closed
opened 2026-09-29 18:05:43 +02:00 by erikinkinen · 1 comment
Owner

Summary

The binding-client host transcript writes the authority count into the last word of the begin-configuration request. The canonical fixture already ends in the supplementary-group count, so the published transcript changes G to 18 while leaving A zero. It cannot describe the real binding workload's 18 authority records and three group words.

Reproduction

Read the begin-configuration literal in src/runtime/launch_transport/realm_clients_probe_tests.rs and the op == 0x6d5 adaptation in src/runtime/launch_transport/realm_binding_probe_tests.rs. The former ends with authority count zero followed by group count three; the latter overwrites its last eight bytes with 18. Compare these fields with the explicit counted request contract.

Expected and actual behavior

Expected: the binding transcript independently retains A=18 and G=3. The descriptor-storage extension also needs its distinct F=10 field.

Observed in source: selecting the last word conflates different count families. Use the literal published offsets, accounting for the transcript's omitted request-ID prefix, to update A and F while retaining G. Preserve the original client lifecycle, source receipt and retirement assertions.

Environment and identity

  • Exsh branch feature/posix-compat; published base 836d2da2606e5f5152f1de293b923b95eb475d46.
  • Source inspection of authored host transcript, with descriptor-storage migration in progress.
  • No compiler, host test, image, VM or CI run was performed. Last passing transcript revision is not established.
  • This correction changes expected descriptive request bytes and grants no native authority.

Evidence and prior checks

Implemented in signed source 7e35c918. Literal authority and runtime-fd offsets now preserve the independent supplementary-group count in the binding transcript. Existing lifecycle controls are retained. This is source/formatting evidence only; this source excerpt does not establish complete compiler, test, CI or native-workload acceptance.

The mismatch is visible in the two literal source constructions. This report records a source defect, not an observed executed-test failure. Tests and CI observation remain deferred by user instruction. Keep the transcript independent of the production encoder and preserve both complete count families.

Tracking

Related ownership design: erix/posixd#15. Owning review: #3. Phase tracking: erix/integration#65.

## Summary The binding-client host transcript writes the authority count into the last word of the begin-configuration request. The canonical fixture already ends in the supplementary-group count, so the published transcript changes G to 18 while leaving A zero. It cannot describe the real binding workload's 18 authority records and three group words. ## Reproduction Read the begin-configuration literal in `src/runtime/launch_transport/realm_clients_probe_tests.rs` and the `op == 0x6d5` adaptation in `src/runtime/launch_transport/realm_binding_probe_tests.rs`. The former ends with authority count zero followed by group count three; the latter overwrites its last eight bytes with 18. Compare these fields with the explicit counted request contract. ## Expected and actual behavior Expected: the binding transcript independently retains A=18 and G=3. The descriptor-storage extension also needs its distinct F=10 field. Observed in source: selecting the last word conflates different count families. Use the literal published offsets, accounting for the transcript's omitted request-ID prefix, to update A and F while retaining G. Preserve the original client lifecycle, source receipt and retirement assertions. ## Environment and identity - Exsh branch `feature/posix-compat`; published base `836d2da2606e5f5152f1de293b923b95eb475d46`. - Source inspection of authored host transcript, with descriptor-storage migration in progress. - No compiler, host test, image, VM or CI run was performed. Last passing transcript revision is not established. - This correction changes expected descriptive request bytes and grants no native authority. ## Evidence and prior checks Implemented in [signed source `7e35c918`](https://git.erikinkinen.fi/erix/exsh/commit/7e35c91837cc20c78c63fa66fe1d361c77234dae). Literal authority and runtime-fd offsets now preserve the independent supplementary-group count in the binding transcript. Existing lifecycle controls are retained. This is source/formatting evidence only; this source excerpt does not establish complete compiler, test, CI or native-workload acceptance. The mismatch is visible in the two literal source constructions. This report records a source defect, not an observed executed-test failure. Tests and CI observation remain deferred by user instruction. Keep the transcript independent of the production encoder and preserve both complete count families. ## Tracking Related ownership design: https://git.erikinkinen.fi/erix/posixd/issues/15. Owning review: https://git.erikinkinen.fi/erix/exsh/pulls/3. Phase tracking: https://git.erikinkinen.fi/erix/integration/issues/65.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:49 +01:00
Author
Owner

The credential-stage transcript is now separated in #60. It keeps A=16 and G=3 in distinct words, places groups after the authority records, and includes every group append in the lifecycle checks. The later resize and runtime-fd budgets remain separate changes.

The credential-stage transcript is now separated in #60. It keeps A=16 and G=3 in distinct words, places groups after the authority records, and includes every group append in the lifecycle checks. The later resize and runtime-fd budgets remain separate changes.
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/exsh#11
No description provided.