[BUG] Provider-read frame checker uses the retired request-loop symbol #38
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/vfsd#38
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 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
b41aaa4b3b27f93ce718409cf662503c98e78100with the runtime PIC configuration, then runscripts/check-provider-read-frames.pyagainst that ELF. The first run exits 1 withmissing 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
b41aaa4band LibIPC9e32c525. 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
dae0e1f4405afa77a4e7ca698278a24bc9541f94changes 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
Implementation: PR #3. Related work: owned namespace migration.
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.