[BUG] Provider cleanup refusal can send a rolled-back lock success #28
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#28
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
Source audit confirms that private acquisition-scope cleanup can roll back an original advisory lock change, then refuse provider retirement while leaving its saved success reply available to native serving. The original caller can receive Complete even though its lock is absent. This concerns result consistency for an operation within the original admitted scope.
Reproduction
The smallest source scenario has one original native call; parallel intake is not required:
The new control
provider_refusal_cannot_publish_the_original_cached_lock_success_after_rollbackuses the actual scope/provider fixture, an independent native owner and peer lock observations. It is authored but unrun; no runtime reproduction, frequency or clean-image pass is claimed.Expected and actual behavior
Expected: beginning authenticated private retirement permanently abandons the original saved result before fallible cleanup. Native history and original provider/receiver/call custody remain retained through positive retirement and disposal.
Actual source behavior: reply abandonment occurs only after provider cleanup succeeds, so a Busy return leaves the saved lock success eligible for COMPLETE despite rollback.
Environment and identity
Evidence and prior checks
The affected
retire_acquisition_scoperolls back advisory state before fallible provider cleanup, but suppresses only the receiver row's reply afterward.finish_exact_invocationsees remaining metadata and can attempt that saved result. Authored regression source distinguishes the original native result, peer lock coverage and retained cleanup identity. Additional written controls cover permanent abandonment, original completion history, malformed rosters and multiple-call native/receiver drain. Tests, builds and CI observation remain deferred by request.Tracking
Independent native invocations, local stream sockets, Phase 6 completion. Related reviews: Vfsd, Docs, Integration.
Regression criteria
Source repair — 4 October 2026
The full concurrent serving and socket requirements remain open.
erikinkinen referenced this issue2026-10-04 07:27:08 +02:00
erikinkinen referenced this issue from erix/docs2026-10-04 07:27:08 +02:00
erikinkinen referenced this issue from erix/integration2026-10-04 07:27:08 +02:00
erikinkinen referenced this issue from erix/posixd2026-10-04 09:33:55 +02:00