[FEATURE] Create temporary objects and atomically replace build outputs #30
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/posixd#30
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
Build tools need exclusive temporary files and directories plus atomic publication in their delegated output trees. The existing native creation and rename effects need a reusable client composition and combined lifetime controls.
Proposed behavior and scope
Add a bounded client operation over the existing compatibility protocol: six trailing template characters, explicit caller-supplied seed and path/base, read-write exclusive file creation at mode 0600 or directory creation at mode 0700. Only a fully correlated EEXIST with retired original caller permits advancing to another candidate. Enumerate the complete six-character alphabet without an arbitrary retry count. Use existing original-entry rename for atomic output replacement, retaining open source and displaced-object lifetime and explicit same-filesystem constraints.
Authority, security and reliability
Use only the admitted client ingress and its original root/cwd/dirfd ceiling. Do not discover a temporary directory, read environment paths, acquire entropy, change umask or add capabilities. Candidate names are descriptive, not secrets or entropy. Native exclusive creation remains the race boundary. Preserve original caller custody on incomplete or uncertain effects. An unreported successful creation is not automatically unlinked by spelling. Atomic visibility and crash durability are separate: existing file and directory sync retain their actual provider guarantees.
Acceptance criteria
Checklist
Alternatives and tradeoffs
Compose existing exclusive creation and conditional rename instead of adding another wire opcode or provider mutation. A caller-supplied candidate seed avoids hidden clock, process, environment or entropy dependencies. Complete candidate-space exhaustion is a real finite representation limit; transport and filesystem errors are returned without search or replay. Predictable candidates are unsuitable as secrets. C entry points remain part of the separately tracked libc runtime integration.
Tracking and rollout
Coordinate filesystem semantics, namespace lifetime, Posixd review and phase completion. Tests, builds, lint, generated documentation, VM/profiler execution and CI observation remain deferred under the execution waiver. Authored controls are unrun. Both full EriX guest generations and external Rust/LLVM guest rebuilding remain required.
Temporary objects and atomic output completion — 2 October 2026
Full libc integration, both full EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed.
Related records and contracts
erikinkinen referenced this issue from erix/docs2026-10-02 08:05:41 +02:00
erikinkinen referenced this issue from erix/integration2026-10-02 08:05:42 +02:00
erikinkinen referenced this issue2026-10-02 08:05:43 +02:00
erikinkinen referenced this issue from erix/rootd2026-10-02 08:05:44 +02:00