[FEATURE] Audit authority, code quality and documentation in dynlinkd #2
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/dynlinkd#2
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?
Problem and motivation
Audit
dynlinkdthroughout Phase 6. Validate admitted dynamic objects and prepare dependency, symbol and relocation plans for authorized process materialization.Review each changed boundary at the final published revision. Prioritize security, reliability, then performance.
Proposed behavior and scope
Current inventory: 1 Cargo target (1 bin); manifests:
Cargo.toml. Include explicit and automatically discovered targets, supported features and target-specific configurations.Inventory every startup/runtime grant and authenticated peer, then success, denial, cancellation, failed transfer, restart and teardown. Trace callers and downstream providers so names, numeric identities and retained aliases never become implicit authority.
Authority, security and reliability
Record each finding's affected revision, invariant, reproduction, owner, regression coverage and resolution. Report suspected vulnerabilities through SECURITY.md and keep sensitive details private. Record a result and rationale for each audit criterion, including caller responsibilities when this component has no process or Rust target.
Acceptance criteria
Checklist
missing_docsenforcement without blanket allowances or hidden-API escapes, warning-denied private-item rustdoc and an undocumented-public-API negative gate.cargo fmt --all -- --check, strict Clippy, unit/doctests and warning-denied builds/rustdoc for every owned crate/target under default and all valid feature, freestanding/host, SMP and profile combinations; test mutually exclusive combinations separately. Add focused VM regressions for runtime behavior and observe the older catalog and unit tests at the exact published heads.Alternatives and tradeoffs
Refactor within the component unless shared semantics justify extracting common code. Preserve regression coverage before deleting superseded paths. Profile before optimizing, and document ABI limits, hardware limits and explicit quotas. Preserve security and reliability requirements.
Tracking and rollout
Retained transaction cleanup — 25 September 2026: signed Dynlinkd b3338336 preserves any live predecessor when a new begin is refused and accepts repeated abort only for the original transaction or positively idle state. Coordinated Loaderd/Procd cleanup and native acceptance remain open in PR3.
Retained cleanup design — 25 September 2026: lifecycle failures must return the exact original materialization and linker transaction owners to a cleanup-only boundary. Each owner advances independently and is removed only after correlated acknowledged disposition; ordinary request serving remains unavailable while either is unresolved. Complete linker cleanup precedes process commit. An idempotent Abort confirms an already idle peer, while a different active transaction remains refused and a new Begin preserves any live predecessor. Procd must retain and advance failed cleanup before it can acknowledge absence. Existing operation widths and authority routes remain unchanged. Source implementation, whole-graph fault controls, coherent dependency validation and native evidence are required before acceptance.
feature/posix-compat; update linked WIP PRs after coherent signed checkpoints using canonical CONTRIBUTING.md messages.c1d6502fad057d35915141157d0af2bf335a8c01; refresh component/dependency heads and their own CI evidence as implementation advances.[FEATURE] [P02.R15] Audit authority, code quality and documentation in dynlinkdto [FEATURE] Audit authority, code quality and documentation in dynlinkd