[BUG] Provider-read frame checker uses the retired request-loop symbol #38

Closed
opened 2026-10-20 16:33:18 +02:00 by erikinkinen · 1 comment
Owner

Summary

The provider-read frame checker still uses the old request-loop symbol after the runtime module split. It rejects the built runtime before checking the complete chain. This is a checker regression; no stack overflow was observed.

Reproduction

Build Vfsd b41aaa4b3b27f93ce718409cf662503c98e78100 with the runtime PIC configuration, then run scripts/check-provider-read-frames.py against that ELF. The first run exits 1 with missing emitted provider read proof: vfsd::runtime::serve_requests.

Expected and actual behavior

The checker should include vfsd::runtime::requests::serve_requests, which is present in the emitted disassembly. It asks for the former module path instead. The fixture derived its expected names from the checker's own list, so it missed this drift.

Environment and identity

Hosted x86-64, Rust 1.97.1, Vfsd b41aaa4b and LibIPC 9e32c525. The runtime PIC configuration, 240 KiB fixed-chain allowance and 256 KiB deployment stack are unchanged. No guest reproduction or last working revision was established.

Evidence and prior checks

The original binary, disassembly and failure are retained. Published repair dae0e1f4405afa77a4e7ca698278a24bc9541f94 changes only the selector and Python fixtures. Both actual emitted frame proofs now use 133,488 of the original 245,760 bytes. The fixtures use an independent literal chain and reject the old symbol and an oversized late request-loop frame.

Tracking

  • Correct the emitted request-loop selector without changing the required chain or stack allowance.
  • Add independent fixtures for the old selector and the complete current chain.
  • Check both built runtime configurations with the original frame budget.
  • Observe the repaired checker in the original CI run for the published source.

Implementation: PR #3. Related work: owned namespace migration.

## Summary The provider-read frame checker still uses the old request-loop symbol after the runtime module split. It rejects the built runtime before checking the complete chain. This is a checker regression; no stack overflow was observed. ## Reproduction Build Vfsd `b41aaa4b3b27f93ce718409cf662503c98e78100` with the runtime PIC configuration, then run `scripts/check-provider-read-frames.py` against that ELF. The first run exits 1 with `missing emitted provider read proof: vfsd::runtime::serve_requests`. ## Expected and actual behavior The checker should include `vfsd::runtime::requests::serve_requests`, which is present in the emitted disassembly. It asks for the former module path instead. The fixture derived its expected names from the checker's own list, so it missed this drift. ## Environment and identity Hosted x86-64, Rust 1.97.1, Vfsd `b41aaa4b` and LibIPC `9e32c525`. The runtime PIC configuration, 240 KiB fixed-chain allowance and 256 KiB deployment stack are unchanged. No guest reproduction or last working revision was established. ## Evidence and prior checks The original binary, disassembly and failure are retained. Published repair `dae0e1f4405afa77a4e7ca698278a24bc9541f94` changes only the selector and Python fixtures. Both actual emitted frame proofs now use 133,488 of the original 245,760 bytes. The fixtures use an independent literal chain and reject the old symbol and an oversized late request-loop frame. ## Tracking - [x] Correct the emitted request-loop selector without changing the required chain or stack allowance. - [x] Add independent fixtures for the old selector and the complete current chain. - [x] Check both built runtime configurations with the original frame budget. - [x] Observe the repaired checker in the original CI run for the published source. Implementation: [PR #3](https://git.erikinkinen.fi/erix/vfsd/pulls/3). Related work: [owned namespace migration](https://git.erikinkinen.fi/erix/lib-ipc/issues/12).
erikinkinen 2026-10-20 16:33:18 +02:00
Author
Owner

Fixed in dae0e1f4. Original CI 394 passes both emitted provider-read proofs at 133,488 of 245,760 bytes. The stack allowance and required chain are unchanged.

Fixed in `dae0e1f4`. [Original CI 394](https://git.erikinkinen.fi/erix/vfsd/actions/runs/394) passes both emitted provider-read proofs at 133,488 of 245,760 bytes. The stack allowance and required chain are unchanged.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:20 +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/vfsd#38
No description provided.