[BUG] Serve owned native clock requests on the delegated public endpoint #3
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/timed#3
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 realm mediator submits clock observations using owned native SUBMIT, but Timed's public service only receives and replies using legacy IPC. It neither registers the public endpoint for owned requests nor claims/completes that queue. Kernel owned SUBMIT requires an explicit live receiver registration and otherwise returns NOT_FOUND before accepting a caller. Consequently the configured native clock path cannot reach Timed's existing clock handler.
Reproduction
Source inspection at the revisions below establishes the incompatible producer/consumer contracts: follow Posixd ClockQuery::advance through Caller::submit and native invocation::submit; Kernel invocation/admission.rs rejects a missing registered receiver; Timed service_loop exclusively uses recv_message_with_timeout and legacy reply helpers. Search the complete Timed source for register_receiver, CLAIM and COMPLETE; no owned public intake exists. An actual realm-clock VM or warning-denied host/native build has not been executed under the current testing waiver. Runtime frequency and last working artifact are not claimed.
Expected and actual behavior
An explicitly delegated realm Clock/Read observation should reach the actual time provider through matching transport, preserve original native caller/serving ownership and return correlated time evidence. The source-selected route currently fails owned native admission with NOT_FOUND and no accepted caller. Legacy clock callers remain a separate working contract; their presence does not register an owned receiver.
Environment and identity
ce25c6812f552ab9ad5c3a193af0e40182ea84ad.3e9f22d7092b38658d4b7595fc4b26bac83b773c.702525fa50599cda14f57d6bfee6d97c4ca2d136.d690a124ca87d7a4a5a8d58daf6dd4df1c99acea; feature branchfeature/posix-compat.Evidence and prior checks
The producer implementation is Posixd src/realm_io/external/clock/query.rs; the kernel requirement is src/kobj/endpoint/invocation/admission.rs; the consumer is Timed src/main.rs service_loop. Repair must serve owned calls through the existing actual public endpoint, preserve legacy callers and original cancellation/retirement, and author transport-level controls using a receiver registration requirement instead of a fixture that blindly accepts submitted clock frames. Tests/builds/CI remain deferred.
Tracking
Prerequisite for race-free descriptor readiness and phase completion. Implement the actual provider transport and independent regression controls without adding native grants or falling back to a fabricated time source.
Owned public clock transport repair — 2 October 2026
No new grant, private RTC route, clock-adjustment authority or hidden clock lookup is introduced.
Legacy receive calls are nonblocking so they cannot park the daemon while the separate owned queue has work. Definite short-result-budget rejection permits one empty refusal on the same owner, without resampling; uncertain publication retains custody through original cancellation and acknowledgment.
The complete descriptor-readiness feature remains open: native atomic sleep/wakeup, explicit monotonic deadlines, original descriptor subscriptions, actual mediator/provider consumers, signal/cancellation behavior and native workloads are still unfinished. This prerequisite adds no checklist acceptance. Both full guest EriX generations and external Rust/LLVM rebuilding remain required and unperformed.
Related records and contracts
erikinkinen referenced this issue from erix/docs2026-10-02 10:22:20 +02:00
erikinkinen referenced this issue from erix/integration2026-10-02 10:22:21 +02:00
erikinkinen referenced this issue from erix/posixd2026-10-02 10:22:22 +02:00