[BUG] Preserve separate authority and group counts in the binding transcript #11
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/exsh#11
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
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.rsand theop == 0x6d5adaptation insrc/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
feature/posix-compat; published base836d2da2606e5f5152f1de293b923b95eb475d46.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.
erikinkinen referenced this issue from erix/docs2026-09-29 18:25:23 +02:00
erikinkinen referenced this issue2026-09-29 18:26:25 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 18:27:07 +02:00
erikinkinen referenced this issue from erix/launchd2026-09-29 18:27:27 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-09-29 18:27:33 +02:00
erikinkinen referenced this issue from erix/lib-posixabi2026-09-29 18:27:36 +02:00
erikinkinen referenced this issue from erix/loaderd2026-09-29 18:27:40 +02:00
erikinkinen referenced this issue from erix/posixd2026-09-29 18:27:43 +02:00
erikinkinen referenced this issue from erix/procd2026-09-29 18:27:45 +02:00
erikinkinen referenced this issue from erix/rootd2026-09-29 18:27:47 +02:00
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.