[BUG] Final source cleanup can leave local peers parked #39

Closed
opened 2026-10-03 00:51:23 +02:00 by erikinkinen · 0 comments
Owner

Summary

Final original-source cleanup can retire a local pipe/socket end or stop/drain a listener before its enclosing native serving owner retires. These local changes were not reported to the serving activity scheduler, so an already parked peer could remain asleep until unrelated activity or a later completion.

Reproduction

Source-derived sequence: park a peer readiness call at a fixed native activity epoch; retain an ordinary source after an effect-free replacement refusal; close the source fd while that hold survives; then let final source cleanup retire the writer while the native serving owner remains live. The peer needs to observe HANGUP without waiting for another native epoch or successful completion of the refused call.

A regression control is being authored for that exact sequence. No compiler, unit-test, VM or CI execution was performed; runtime reproduction is not yet established.

Expected and actual behavior

Expected: every committed local listener/queue change wakes parked peer observation immediately, independently of native result publication and final source ownership retirement.

Observed in source: release_source returned only a completion boolean. Ordinary final cleanup ignored local wake information, and readiness cleanup returned Pending after releasing an end or backlog entry. The ordinary scheduler automatically reports only Prepared, Completed and Retired outcomes. Local cleanup could instead yield RetirementPending or Waiting with no revision change. No runtime diagnostic or exit status was collected.

Environment and identity

  • Component repository/revision and Integration source graph: Posixd c77a64b9ceeef5c58bbff1c72f27f3c969582bb9; Integration 756d23c9d0742761a0f932382803bfb983631a99.
  • Image profile, digest and build/runtime configuration: activity-gated local source cleanup; no image built.
  • Hardware or VM, architecture, firmware and toolchain versions: not executed.
  • Input/session route and granted authority relevant to reproduction: original sealed client ingress and retained pipe/socket source; no added native grant.
  • Last known working revision, if known: not established.

Evidence and prior checks

Source audit of channel/held_cleanup, serving/source, serving/readiness/progress and serving/activity. Cleanup completion and local activity must be represented separately, including partial listener backlog disposal. The correction also reports cancelled alias intent/target restoration activity. Tests and CI observation remain deferred by request.

Tracking

Related: local stream sockets, mediator review, phase completion.

Source resolution — 3 October 2026

A new same-epoch control checks peer HANGUP while the refused original native call remains owned, and existing controls assert no repeated wake after settled cleanup.

## Summary Final original-source cleanup can retire a local pipe/socket end or stop/drain a listener before its enclosing native serving owner retires. These local changes were not reported to the serving activity scheduler, so an already parked peer could remain asleep until unrelated activity or a later completion. ## Reproduction Source-derived sequence: park a peer readiness call at a fixed native activity epoch; retain an ordinary source after an effect-free replacement refusal; close the source fd while that hold survives; then let final source cleanup retire the writer while the native serving owner remains live. The peer needs to observe HANGUP without waiting for another native epoch or successful completion of the refused call. A regression control is being authored for that exact sequence. No compiler, unit-test, VM or CI execution was performed; runtime reproduction is not yet established. ## Expected and actual behavior Expected: every committed local listener/queue change wakes parked peer observation immediately, independently of native result publication and final source ownership retirement. Observed in source: release_source returned only a completion boolean. Ordinary final cleanup ignored local wake information, and readiness cleanup returned Pending after releasing an end or backlog entry. The ordinary scheduler automatically reports only Prepared, Completed and Retired outcomes. Local cleanup could instead yield RetirementPending or Waiting with no revision change. No runtime diagnostic or exit status was collected. ## Environment and identity - Component repository/revision and Integration source graph: Posixd `c77a64b9ceeef5c58bbff1c72f27f3c969582bb9`; Integration `756d23c9d0742761a0f932382803bfb983631a99`. - Image profile, digest and build/runtime configuration: activity-gated local source cleanup; no image built. - Hardware or VM, architecture, firmware and toolchain versions: not executed. - Input/session route and granted authority relevant to reproduction: original sealed client ingress and retained pipe/socket source; no added native grant. - Last known working revision, if known: not established. ## Evidence and prior checks Source audit of channel/held_cleanup, serving/source, serving/readiness/progress and serving/activity. Cleanup completion and local activity must be represented separately, including partial listener backlog disposal. The correction also reports cancelled alias intent/target restoration activity. Tests and CI observation remain deferred by request. ## Tracking Related: [local stream sockets](https://git.erikinkinen.fi/erix/posixd/issues/34), [mediator review](https://git.erikinkinen.fi/erix/posixd/pulls/5), [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). ### Source resolution — 3 October 2026 A new same-epoch control checks peer HANGUP while the refused original native call remains owned, and existing controls assert no repeated wake after settled cleanup.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:08 +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/posixd#39
No description provided.