generated from erix/meta
[FEATURE] Audit authority, code quality and documentation in lib-posixabi #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/lib-posixabi#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
lib-posixabithroughout Phase 6. Implement the planned POSIX wire and C ABI contracts, keeping compatibility identifiers and credentials separate from native grants.Review each changed boundary at the final published revision. Prioritize security, reliability, then performance.
Proposed behavior and scope
Current targets: none; scaffolded from meta. Add every future library, executable, build script, example and test target to this audit before implementation acceptance.
The repository currently contains the verified meta template and no Rust implementation. Audit the scaffold now, then every implemented compatibility boundary; absence of a current target does not close future implementation rows.
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
PR2 remains unfinished for its broader scope; full ABI, native client-lifecycle execution and both guest rebuilds remain required.
feature/posix-compat; update linked WIP PRs after coherent signed checkpoints using canonical CONTRIBUTING.md messages.74ea167d14a7ad05bb436d47e9692122f640f5ee; refresh component/dependency heads and their own CI evidence as implementation advances.No local API or capability policy changes. Actual service consumer and coherent full VM adoption remain open in phase completion.
Counted namespace intents and original raw readlink — 1 October 2026
Unused fields are canonical zero; names and symbolic targets carry no native authority.
Only the admitted prefix is staged; actual counted storage exhaustion refuses without silently shortening success. Final target bytes are never traversed, no content grant or fd is acquired, and all original callers, parents, links and expansion owners retire before delivery.
Complete mutation permission/effect mediation, two-path rename/link, legacy cwd migration and ext/FAT conditional transactions remain unfinished. Raw readlink is split from the previous combined two-path criterion to record one fully implemented operation boundary; the full namespace parent remains open. The existing native binding workload now requires seven raw-target observations/refusals per peer, including readlinkat and the read-only scope, without new authority or fixture budgets.
Both complete EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed.
Original-entry namespace mutation mediation — 1 October 2026
Hardlink source requires parent search; changed directories require write/search.
Ordinary final-link/trailing-directory probes cannot substitute for entry evidence. Cleanup cannot undo a completed mutation.
The independent filesystem model keeps real initial directory entries, so a removed name cannot reappear from a fixture fallback.
They cover independent dirfds, link following, same-object rename, complete ACL/sticky policy, exact refusals, original detached content, cancellation and uncertain completion. The read-only peer requires all five mutation families to refuse.
The exact wire/migration, actual permission/effect mediation and two-path semantic criteria are source-accepted. The full namespace parent stays open: legacy cwd migration, required ext/FAT conditional transactions and cross-provider lifetime remain unfinished. Both complete EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed.
Related records and contracts
[FEATURE] [P02.R74] Audit authority, code quality and documentation in lib-posixabito [FEATURE] Audit authority, code quality and documentation in lib-posixabierikinkinen referenced this issue2026-09-12 09:45:06 +02:00
erikinkinen referenced this issue2026-09-25 03:20:34 +02:00