[FEATURE] Audit authority, code quality and documentation in e2fsd #1

Open
opened 2026-09-12 07:57:34 +02:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Audit e2fsd throughout Phase 6. Serve ext-family filesystem operations over explicit block/key grants and retained exact inode/directory handles.

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
  • Record origin, recipient, object, operations, delegation ceiling, lifetime and aliases for each relevant capability or caller-supplied authority-bearing value.
  • Audit ambient discovery/selectors, cwd/PATH/environment, numeric identities, inherited routes and host fallbacks; require explicit authorized intake.
  • Account for residual authority after success, error, cancellation, timeout, restart, failed transfer and teardown, including fork/exec where implemented.
  • Remove unnecessary endpoints, broad rights, duplicate aliases, provider/admin grants and debug routes.
  • Exercise stale generations, replay, pending replies, forged descriptive identity and object/path resolution races at the owned boundary.
  • Prove independent cleanup attempts and caller-specific error precedence; quarantine or terminate when retained authority cannot be accounted for.
  • Review unsafe/FFI/parser/arithmetic/lifetime/lock/publication invariants and add adversarial coverage where practical.
  • Inventory obsolete APIs, wrappers, fallback/dead paths and duplicate validators with their maintained callers.
  • Migrate callers and delete deprecated contracts/shims in a coherent signed revision graph; reject retired input versions where relevant.
  • Classify each size/count/depth/time bound as ABI, hardware, explicit resource policy or accidental limitation.
  • Test beyond removed boundaries and at allocation/ABI limits while preserving exhaustion errors, denial-of-service controls and bounded waits.
  • Keep every tracked authored code/test/script/workflow file below 1000 physical lines through thematic refactoring.
  • Run the deterministic tracked-source size gate, covering executable fixtures/generators and excluding only genuine non-code data or external payloads.
  • Audit production/test feature and symbol separation, including this repository's effect on rootd test orchestration.
  • Supply changes affecting rootd semantic surface to the maintained same-toolchain baseline; record a justified component-specific applicability result.
  • Check bootstrap ownership and development/release authority parity at this repository's producer/consumer boundary.
  • Use maintained integration#3 profiler evidence before optimizing; preserve live access checks, ownership and success criteria.
  • Audit build/CI inputs, secret handling, private outputs, symlink containment, deletion, subprocess bounds, warnings and host dependencies.
  • meaningful public/private inline documentation, crate/target missing_docs enforcement without blanket allowances or hidden-API escapes, warning-denied private-item rustdoc and an undocumented-public-API negative gate.
  • Validation: Run 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.
  • Documentation: update applicable README/ARCHITECTURE/ROADMAP in meta's canonical format and affected technical-manual TeX/API references; keep README evergreen and shared governance byte-identical to meta.
  • Evidence: record exact source/dependency revisions, commands, configurations, real exit status, CI run URLs and results; repeat the audit on final heads and obtain independent review of security closures. No skipped/pending/predecessor result counts as a pass.

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.

Matching catalog adoption and real consumer VMs remain requirements; complete realm and full in-guest build acceptance remain open.

Original coherent realm source CI acceptance — 18 September 2026: Signed 4d8dda85e3c24daecc2b854289a923ec70485c3a passes CI 179 and CI 178. Coherent catalog publication, actual consumer VMs and full guest-build acceptance remain separate open requirements.

Tracking and rollout

All 34 maintained local checks pass: development/release feature matrices (264 unit tests per selection), strict host/native Clippy, warning-denied builds, private rustdoc, applicable doctests and component-specific checks, formatting and exact dependency-source validation. Native binaries have executable read-only entry pages and no writable executable pages. Original CI186 and CI187 pass; their complete logs are independently reviewed with zero warnings. No unchanged CI was rerun. Coordinated VM configuration/seal/four-client I/O, repeated managed-row reuse, profiler observation and both full builds inside EriX remain open under the phase checklist. This dependency work earns no separate feature-completion credit.

All 4 selected development/release configurations pass (264 unit tests per configuration). Strict host/native Clippy, warning-denied host/native builds, doctests where provided, private rustdoc, formatting, Markdown and dependency checks pass with zero warnings. Filesystem tests use the explicitly selected, hash-verified fixture tools.

Matching-image native Posixd startup, two-realm independence and retirement acceptance remain pending. These local checks do not establish sealing, client I/O, a complete EriX guest build or the external toolchain rebuild. Publication CI is tracked separately from local validation.

VFS requires frozen Write for regular-file resize and live admitted file/directory custody for sync. Known refusals preserve original admission; uncertainty keeps cleanup-only custody, with no retry or pathname reopen.

No request or adapter adds a device, mount, credentials, new native rights or capability transfer.

They cover literal framing, unchanged output on refusal, full correlation, access direction, actual aliases and zero growth, storage/format refusal, clean recovery ownership, lost barriers/replies, retained cleanup and short reply capacity.

Existing ext logical-range conversions and sparse-gap traversal still need the size-boundary audit; compatibility truncate/ftruncate/fsync/fdatasync consumers, complete cancellation controls and new live workloads remain unfinished. Current phase completion remains 19.20% weighted, 7.61% whole acceptance: 27/460 parents and 486/949 children.

Both full guest EriX generations and external Rust/LLVM rebuilding remain required and unperformed.

Detailed scope and contracts

Original filesystem persistence — signed source acceptance, 2 October 2026

Compatibility truncate/ftruncate and fsync/fdatasync serving, its complete native workloads and full-item acceptance remain open in retained-description persistence.

They separate volatile/persisted bytes and cover writer and full/fast-recovery interruption boundaries, lost replies, partial checkpoints, original routes, capacity/refusal, checksum dialects, wrapped descriptors and identities, later revocations, imported superblocks and actual clock-free file operations.

Source acceptance is not an executed persistence result, warning-free build or measured speedup. Both full EriX guest generations and external Rust/LLVM rebuilding in EriX remain required and unperformed.

Phase progress is 19.20% weighted, 7.61% whole acceptance: 27/460 parents and 486/949 children.

Cross-provider filesystem lifetime — signed source acceptance, 2 October 2026

Two live binding scenarios cover RAM, ext and separately selected FAT32/exFAT: conditional replacement/unlink, retained aliases and original identities, moved/detached directories, name reuse, supported links and read-only, cross-filesystem and unsupported-link refusals. Final media observers require reclaimed allocations, consistent reverse indices and clear undo ownership.

Both full EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed.

Phase progress: 19.12% weighted, 7.61% whole acceptance; 27/460 parents and 485/949 sub-items.

Explicit fixture selection checkpoint — 15 September 2026

Signed da51754b1c871dfdee81c20920a8074ac105a4cb requires an explicitly selected absolute fixture generator, removes implicit checkout discovery and the obsolete directory selector, and selects/hashes the original generator in CI. Product VM and full guest build acceptance remain pending.

Full catalog equality and actual consumer-image validation remain required under Integration regression 68. This dependency checkpoint does not close full lifecycle, frame or self-hosting acceptance.

Full service CPU/profiler VM acceptance and guest builds remain open in Phase 6 completion.

Original namespace mutation plan and provider custody — 1 October 2026

The complete namespace feature remains open.

Known pre-effect refusal preserves original pending custody; existing-object touch and absent no-create observations retain their distinct lifetimes.

They cover original-name admission, actual RAM/literal-ext effects, hardlink entry distinction, known refusal, completed-operation retirement, cleanup and namespace reuse.

The namespace umbrella now checks its completed status/directory criterion, matching the already accepted feature and phase master. No new namespace criterion is accepted for the provider prerequisite. Both complete EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed.

Conditional retained-entry namespace custody — 1 October 2026

Exact response correlation distinguishes completed effects, definite no-effect refusals and uncertainty.

Missing, malformed or uncorrelated replies preserve cleanup and never permit replay. The installed namespace is currently immutable and append-only; future unmount/reconfiguration requires a persistent nonwrapping epoch.

Ext and FAT return explicit correlated unsupported no-effect dispositions for the new family. Their conditional transactions remain unfinished. Complete compatibility path/dirfd, ACL/sticky, final-link and trailing-separator mediation and legacy cwd migration remain open in the owning design. Required legacy cwd and administrative spelling guards remain.

Thirty-nine new Rust controls are authored and unrun: ten literal wire controls, seventeen RAM provider controls, eight actual Vfsd dispatch controls, and two explicit-refusal controls each for ext and FAT.

Both complete EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed.

Disk namespace transaction and lifetime design — 1 October 2026

The next implementation completes conditional ext/FAT entry effects before migrating legacy cwd consumers. Each selection retains its original root, parent, fixed role, full basename, binding freshness and permission fingerprint. Target observations remain metadata-only. Both roles are consumed once before the conditional effect; stale, cross-filesystem and invalid evidence must refuse without publishing a name.

Ext will use its existing metadata transaction owner and standard persistent orphan representation to retain unlinked inodes until original handles, entry owners and detached directory ancestry retire. Final reclamation and recovery must preserve inode generations, block ownership, checksums, ACL value ownership and quota accounting. FAT will use the selected semantic catalog and undo transaction owner for shared object bindings and deferred storage reclamation. Neither implementation may claim rollback after uncertain media publication.

Creation must preserve explicit mode, owner/group, mask, inherited default/access ACLs, raw symbolic targets and original timestamps. Removal, hardlink and rename must share retained-parent mutation cores with existing administrative operations, including atomic replacement and actual ancestry checks. Keep legacy cwd guards until exact-object/launch and redirection callers use original entry custody on every required provider.

Author independent media/provider and lifecycle controls; maintain inline contracts and component/manual documentation. This is a planned implementation boundary, not accepted completion. Tests, builds, lint checks, VM/profiler execution and CI observation remain deferred by instruction. Owning namespace design; complete phase requirements.

Original ext inode lifetime — 1 October 2026

Cleanup-only rows cannot regain ordinary access after refusal, and uncertain lifetime publication permanently disables endpoint state.

Creation beneath a removed directory refuses before allocation, and complete close response storage precedes persistent cleanup.

The existing independent Integration helper selected by Rootd remains unchanged; these component-local changes require no Cargo edge update.

Full provider criteria stay open. Ext/FAT conditional namespace requests still return typed Unsupported; plain ext2 durable detachment, FAT lifetime and legacy cwd migration remain unfinished. Both full EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed.

Conditional ext entry custody design — 1 October 2026

The next provider boundary binds each fixed namespace role to the original retained parent, basename, target generation or observed absence, navigation ceiling and complete permission fingerprint. Entry handles permit permission observations and original-key cleanup; they convey no content access. A nonwrapping mount namespace epoch advances before every namespace mutation attempt, including legacy entry routes, to reject remove/relink substitutions even when inode identity is unchanged. This conservative epoch can invalidate unrelated selections; it avoids an unbounded binding map and never caches authorization.

Selection preflights response and handle capacity, burns its original acquisition key and consumes the original parent observation before publication. Mutation consumes admitted roles once, compares original parent/target evidence and actual bindings under an exclusive provider borrow, then uses the shared media transaction. Cancellation, stale evidence and failed replies retain original cleanup ownership. Existing retained-inode cleanup and legacy cwd spelling guards remain in force. Creation policy, directory ACL inheritance, raw symbolic targets and two-parent link/rename belong to the complete implementation. Plain ext2 durability, FAT lifetime and legacy cwd migration remain required. Tests will be authored; execution and CI observation remain deferred.

Conditional journaled ext namespace serving — 1 October 2026

Every legacy and native namespace mutation attempt advances a nonwrapping mount epoch, rejecting remove/relink substitutions even when the inode is unchanged. Entry rows cannot grant content, navigation or ordinary metadata mutation.

Native internal names use ext's 255-byte limit; legacy 240-byte reply rows refuse unrepresentable names without truncation.

They cover original custody and permissions, short/lost replies, binding substitution, all effects, cross-mount refusal, retained content/parents, inherited local/external/streamed ACLs, full names/raw targets, allocation/epoch exhaustion, extended directory counts and uncertain publication.

Full provider/lifetime acceptance remains open. Plain ext2 durable transactions, FAT namespace/lifetime and legacy cwd migration remain unfinished; spelling guards stay until their consumers migrate. Filesystem fsync/device-barrier ordering and both full guest EriX generations and external Rust/LLVM rebuilding remain required and unperformed.

Design: explicitly selected original undo for plain ext2

Plain ext2 will retain its filesystem format and use the already configured same-disk external-journal partition as a separately formatted undo store. An immutable, checksummed footer binds the original filesystem UUID and both partition geometries. Neither discovery, formatting, a fallback journal nor an on-media identifier can grant another block route. The selected original journal is recovered before ordinary filesystem parsing. Read-only mounts cannot repair active media.

A private joined block view exposes exactly the held filesystem extent and the selected journal extent to LibBlock’s existing undo owner. Ordinary callbacks receive only the filesystem prefix. Persistence barriers cover both original routes; target effects become durable before the journal is cleared. Semantic refusal rolls back; uncertainty permanently disables ordinary endpoint use. Mount-time repairs must use the same transaction owner, without nested recovery or an ambient bypass.

Shared ext namespace, timestamp and detached-inode transactions will use this owner on admitted plain media. Original content owners and persistent orphan reclamation retain their existing lifetime rules. Authored controls will cover geometry/UUID substitution, unsupported durability, read-only recovery, rollback, lost completion, original ownership and all namespace effects. Integration will explicitly format/select the fixture partition and add VM scenarios. Documentation will specify the independent on-media format. Tests, builds and CI observation remain deferred by instruction.

Original durable undo for plain ext — 1 October 2026

Runtime mounts never discover, format or replace a journal.

Read-only mounts cannot repair active media; semantic refusal rolls back, while uncertain publication permanently disables ordinary endpoint use. Unselected plain media still refuse effects requiring rollback.

Full namespace/lifetime parents, FAT serving, legacy cwd migration, complete filesystem fsync/JBD2 barriers and both full EriX guest generations plus guest Rust/LLVM rebuilding remain unfinished.

Retire legacy provider pathname and spelling-pin adapters

Current contextual consumers use independently retained native anchors,
conditional component/fixed-entry acquisition and source-free retained effects.
The older provider cwd-open, whole-target readlink and path-selected exact-entry
families now remain in provider dispatch, compatibility adapters and tests.
Inventory every opcode, codec and direct caller before deleting its producer.

Retire cwd component open (0x639), its whole-target link observation (0x63A), and
the obsolete path-selected fixed-entry acquisition/effect adapters where all
ordinary consumers have migrated. Old operation numbers remain unassigned and
must refuse without fallback. Keep actual native metadata, raw link pages,
conditional namespace effects, retained entry effects, original anchors and
acquisition-key retirement. Do not remove ordinary namespace/file interfaces
that still have real users, including generic provider readdir.

Remove cwd spelling-pin fields and their move/unlink guards only after the
corresponding creation paths and dependent tests migrate. Remove legacy exact
binding/parent spelling guards with their final acquisition producers. Preserve
original object, parent and navigation-ceiling ownership; empty directory moves
and detachment must retain actual held objects without pathname reopening or
reuse. Conditional entry freshness, stale-binding refusal, original one-use
effect semantics, permission evidence and positive cleanup remain mandatory.
Imported filesystem-format limits remain explicit and are not bypassed.

Migrate controls to actual native root/anchor/component/fixed-entry acquisition
with original keys known before submission. Do not emulate removed APIs with
test-only path reopeners, fabricated handles, copied identity or renamed legacy
production code. Preserve independent identity/mount separation, maximal ID and
capacity refusal, raw link lifetime, moved/detached ancestors, wrong handle kind,
stale selection/replacement, timestamps, media recovery and cleanup ordering.
Retain literal rejection controls for retired operation numbers. Share cohesive
fixture helpers where useful; all authored code stays below 1,000 lines.

Work through RAM, ext and FAT producers and dependent controls, then remove the
unused shared codecs/IDs and remaining Vfsd adapter references. Publish signed
checkpoints regularly and coordinate adopting immutable dependency revisions.
Update component contracts and authored manual/API addenda. Tests/builds/checks,
generated references, VM/profiler execution and CI observation remain deferred.
Runtime catalogs and both compiled Rootd helper selections remain unchanged
until coherent runtime adoption; full guest EriX and Rust/LLVM rebuilding remains
required. Partial provider retirement does not close the complete lifetime item.

Tracking: codec audit,
RAM audit,
ext audit,
FAT audit,
native ownership,
Phase 6 tracker.

Ordinary V2 response correlation no longer admits retired effect operations.

They retain
root/parent/key fields, full-width handles and timestamps, optional trusted time,
explicit selected fields, invalid destination refusal and untouched short outputs. New literal stat controls cover framing, canaries and retired-family refusal. Retired numeric replies cannot satisfy ordinary V2 or native effect correlation. Vfsd's last old exported-name references become literal timestamp-adapter refusals
for all thirteen retired operations.

The existing superseded-bridge/provider-spelling-pin acceptance criterion in
the native ownership feature
is source-complete. Required imported FAT/exFAT binding and geometry guards remain. The remaining cwd/contextual-serving and complete lifecycle/control/graph criteria
need a current-source acceptance audit and any missing implementation, followed by
coherent runtime adoption. No synthetic weighted sub-item or full lifetime acceptance is added. Recomputed
phase progress remains 18.95% weighted and 6.81% whole acceptance: 25/460 parents
and 480/949 sub-items. Full EriX guest generations and external Rust/LLVM rebuilding
inside EriX remain required and unperformed.

Related records and contracts
Repository Links
docs issue 1, PR 4
docs.kernel.org inodes.html
e2fsd issue 17, PR 3, conditional-namespace.md, detached-inodes.md, original-undo.md
fatd PR 3
integration issue 102, issue 2, PR 12, ext-undo.md
kernel issue 20
lib-ipc PR 2, conditional-namespace.md, retained-exact-entries.md
posixd PR 5, namespace-mutations.md
ramfsd PR 2, PR 3
rootd PR 2
vfsd PR 3
## Problem and motivation Audit `e2fsd` throughout Phase 6. Serve ext-family filesystem operations over explicit block/key grants and retained exact inode/directory handles. 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 <details> <summary>Checklist</summary> - [ ] Record origin, recipient, object, operations, delegation ceiling, lifetime and aliases for each relevant capability or caller-supplied authority-bearing value. - [ ] Audit ambient discovery/selectors, cwd/PATH/environment, numeric identities, inherited routes and host fallbacks; require explicit authorized intake. - [ ] Account for residual authority after success, error, cancellation, timeout, restart, failed transfer and teardown, including fork/exec where implemented. - [ ] Remove unnecessary endpoints, broad rights, duplicate aliases, provider/admin grants and debug routes. - [ ] Exercise stale generations, replay, pending replies, forged descriptive identity and object/path resolution races at the owned boundary. - [ ] Prove independent cleanup attempts and caller-specific error precedence; quarantine or terminate when retained authority cannot be accounted for. - [ ] Review unsafe/FFI/parser/arithmetic/lifetime/lock/publication invariants and add adversarial coverage where practical. - [ ] Inventory obsolete APIs, wrappers, fallback/dead paths and duplicate validators with their maintained callers. - [ ] Migrate callers and delete deprecated contracts/shims in a coherent signed revision graph; reject retired input versions where relevant. - [ ] Classify each size/count/depth/time bound as ABI, hardware, explicit resource policy or accidental limitation. - [ ] Test beyond removed boundaries and at allocation/ABI limits while preserving exhaustion errors, denial-of-service controls and bounded waits. - [ ] Keep every tracked authored code/test/script/workflow file below 1000 physical lines through thematic refactoring. - [ ] Run the deterministic tracked-source size gate, covering executable fixtures/generators and excluding only genuine non-code data or external payloads. - [ ] Audit production/test feature and symbol separation, including this repository's effect on rootd test orchestration. - [ ] Supply changes affecting rootd semantic surface to the maintained same-toolchain baseline; record a justified component-specific applicability result. - [ ] Check bootstrap ownership and development/release authority parity at this repository's producer/consumer boundary. - [ ] Use maintained [integration#3](https://git.erikinkinen.fi/erix/integration/issues/3) profiler evidence before optimizing; preserve live access checks, ownership and success criteria. - [ ] Audit build/CI inputs, secret handling, private outputs, symlink containment, deletion, subprocess bounds, warnings and host dependencies. - [ ] meaningful public/private inline documentation, crate/target `missing_docs` enforcement without blanket allowances or hidden-API escapes, warning-denied private-item rustdoc and an undocumented-public-API negative gate. - [ ] Validation: Run `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. - [ ] Documentation: update applicable README/ARCHITECTURE/ROADMAP in meta's canonical format and affected technical-manual TeX/API references; keep README evergreen and shared governance byte-identical to meta. - [ ] Evidence: record exact source/dependency revisions, commands, configurations, real exit status, CI run URLs and results; repeat the audit on final heads and obtain independent review of security closures. No skipped/pending/predecessor result counts as a pass. </details> ## 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. Matching catalog adoption and real consumer VMs remain requirements; complete realm and full in-guest build acceptance remain open. Original coherent realm source CI acceptance — 18 September 2026: Signed `4d8dda85e3c24daecc2b854289a923ec70485c3a` passes [CI 179](https://git.erikinkinen.fi/erix/e2fsd/actions/runs/179) and [CI 178](https://git.erikinkinen.fi/erix/e2fsd/actions/runs/178). Coherent catalog publication, actual consumer VMs and full guest-build acceptance remain separate open requirements. ## Tracking and rollout All 34 maintained local checks pass: development/release feature matrices (264 unit tests per selection), strict host/native Clippy, warning-denied builds, private rustdoc, applicable doctests and component-specific checks, formatting and exact dependency-source validation. Native binaries have executable read-only entry pages and no writable executable pages. Original [CI186](https://git.erikinkinen.fi/erix/e2fsd/actions/runs/186) and [CI187](https://git.erikinkinen.fi/erix/e2fsd/actions/runs/187) pass; their complete logs are independently reviewed with zero warnings. No unchanged CI was rerun. Coordinated VM configuration/seal/four-client I/O, repeated managed-row reuse, profiler observation and both full builds inside EriX remain open under the [phase checklist](https://git.erikinkinen.fi/erix/integration/issues/65). This dependency work earns no separate feature-completion credit. All 4 selected development/release configurations pass (264 unit tests per configuration). Strict host/native Clippy, warning-denied host/native builds, doctests where provided, private rustdoc, formatting, Markdown and dependency checks pass with zero warnings. Filesystem tests use the explicitly selected, hash-verified fixture tools. Matching-image native Posixd startup, two-realm independence and retirement acceptance remain pending. These local checks do not establish sealing, client I/O, a complete EriX guest build or the external toolchain rebuild. Publication CI is tracked separately from local validation. VFS requires frozen Write for regular-file resize and live admitted file/directory custody for sync. Known refusals preserve original admission; uncertainty keeps cleanup-only custody, with no retry or pathname reopen. No request or adapter adds a device, mount, credentials, new native rights or capability transfer. They cover literal framing, unchanged output on refusal, full correlation, access direction, actual aliases and zero growth, storage/format refusal, clean recovery ownership, lost barriers/replies, retained cleanup and short reply capacity. Existing ext logical-range conversions and sparse-gap traversal still need the size-boundary audit; compatibility truncate/ftruncate/fsync/fdatasync consumers, complete cancellation controls and new live workloads remain unfinished. Current phase completion remains **19.20% weighted**, 7.61% whole acceptance: 27/460 parents and 486/949 children. Both full guest EriX generations and external Rust/LLVM rebuilding remain required and unperformed. <details> <summary>Detailed scope and contracts</summary> ### Original filesystem persistence — signed source acceptance, 2 October 2026 Compatibility truncate/ftruncate and fsync/fdatasync serving, its complete native workloads and full-item acceptance remain open in [retained-description persistence](https://git.erikinkinen.fi/erix/posixd/issues/28). They separate volatile/persisted bytes and cover writer and full/fast-recovery interruption boundaries, lost replies, partial checkpoints, original routes, capacity/refusal, checksum dialects, wrapped descriptors and identities, later revocations, imported superblocks and actual clock-free file operations. Source acceptance is not an executed persistence result, warning-free build or measured speedup. Both full EriX guest generations and external Rust/LLVM rebuilding in EriX remain required and unperformed. Phase progress is **19.20% weighted**, 7.61% whole acceptance: 27/460 parents and 486/949 children. ### Cross-provider filesystem lifetime — signed source acceptance, 2 October 2026 Two live binding scenarios cover RAM, ext and separately selected FAT32/exFAT: conditional replacement/unlink, retained aliases and original identities, moved/detached directories, name reuse, supported links and read-only, cross-filesystem and unsupported-link refusals. Final media observers require reclaimed allocations, consistent reverse indices and clear undo ownership. Both full EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed. Phase progress: **19.12% weighted**, 7.61% whole acceptance; 27/460 parents and 485/949 sub-items. ### Explicit fixture selection checkpoint — 15 September 2026 Signed `da51754b1c871dfdee81c20920a8074ac105a4cb` requires an explicitly selected absolute fixture generator, removes implicit checkout discovery and the obsolete directory selector, and selects/hashes the original generator in CI. Product VM and full guest build acceptance remain pending. Full catalog equality and actual consumer-image validation remain required under [Integration regression 68](https://git.erikinkinen.fi/erix/integration/issues/68). This dependency checkpoint does not close full lifecycle, frame or self-hosting acceptance. Full service CPU/profiler VM acceptance and guest builds remain open in [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). ### Original namespace mutation plan and provider custody — 1 October 2026 The complete namespace feature remains open. Known pre-effect refusal preserves original pending custody; existing-object touch and absent no-create observations retain their distinct lifetimes. They cover original-name admission, actual RAM/literal-ext effects, hardlink entry distinction, known refusal, completed-operation retirement, cleanup and namespace reuse. The [namespace umbrella](https://git.erikinkinen.fi/erix/posixd/issues/2) now checks its completed [status/directory criterion](https://git.erikinkinen.fi/erix/posixd/issues/25), matching the already accepted feature and phase master. No new namespace criterion is accepted for the provider prerequisite. Both complete EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed. ### Conditional retained-entry namespace custody — 1 October 2026 Exact response correlation distinguishes completed effects, definite no-effect refusals and uncertainty. Missing, malformed or uncorrelated replies preserve cleanup and never permit replay. The installed namespace is currently immutable and append-only; future unmount/reconfiguration requires a persistent nonwrapping epoch. Ext and FAT return explicit correlated unsupported no-effect dispositions for the new family. Their conditional transactions remain unfinished. Complete compatibility path/dirfd, ACL/sticky, final-link and trailing-separator mediation and legacy cwd migration remain open in [the owning design](https://git.erikinkinen.fi/erix/posixd/issues/27). Required legacy cwd and administrative spelling guards remain. Thirty-nine new Rust controls are authored and unrun: ten literal wire controls, seventeen RAM provider controls, eight actual Vfsd dispatch controls, and two explicit-refusal controls each for ext and FAT. Both complete EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed. ### Disk namespace transaction and lifetime design — 1 October 2026 The next implementation completes conditional ext/FAT entry effects before migrating legacy cwd consumers. Each selection retains its original root, parent, fixed role, full basename, binding freshness and permission fingerprint. Target observations remain metadata-only. Both roles are consumed once before the conditional effect; stale, cross-filesystem and invalid evidence must refuse without publishing a name. Ext will use its existing metadata transaction owner and standard persistent orphan representation to retain unlinked inodes until original handles, entry owners and detached directory ancestry retire. Final reclamation and recovery must preserve inode generations, block ownership, checksums, ACL value ownership and quota accounting. FAT will use the selected semantic catalog and undo transaction owner for shared object bindings and deferred storage reclamation. Neither implementation may claim rollback after uncertain media publication. Creation must preserve explicit mode, owner/group, mask, inherited default/access ACLs, raw symbolic targets and original timestamps. Removal, hardlink and rename must share retained-parent mutation cores with existing administrative operations, including atomic replacement and actual ancestry checks. Keep legacy cwd guards until exact-object/launch and redirection callers use original entry custody on every required provider. Author independent media/provider and lifecycle controls; maintain inline contracts and component/manual documentation. This is a planned implementation boundary, not accepted completion. Tests, builds, lint checks, VM/profiler execution and CI observation remain deferred by instruction. [Owning namespace design](https://git.erikinkinen.fi/erix/posixd/issues/27); [complete phase requirements](https://git.erikinkinen.fi/erix/integration/issues/65). ### Original ext inode lifetime — 1 October 2026 Cleanup-only rows cannot regain ordinary access after refusal, and uncertain lifetime publication permanently disables endpoint state. Creation beneath a removed directory refuses before allocation, and complete close response storage precedes persistent cleanup. The existing independent Integration helper selected by Rootd remains unchanged; these component-local changes require no Cargo edge update. Full provider criteria stay open. Ext/FAT conditional namespace requests still return typed Unsupported; plain ext2 durable detachment, FAT lifetime and legacy cwd migration remain unfinished. Both full EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed. ### Conditional ext entry custody design — 1 October 2026 The next provider boundary binds each fixed namespace role to the original retained parent, basename, target generation or observed absence, navigation ceiling and complete permission fingerprint. Entry handles permit permission observations and original-key cleanup; they convey no content access. A nonwrapping mount namespace epoch advances before every namespace mutation attempt, including legacy entry routes, to reject remove/relink substitutions even when inode identity is unchanged. This conservative epoch can invalidate unrelated selections; it avoids an unbounded binding map and never caches authorization. Selection preflights response and handle capacity, burns its original acquisition key and consumes the original parent observation before publication. Mutation consumes admitted roles once, compares original parent/target evidence and actual bindings under an exclusive provider borrow, then uses the shared media transaction. Cancellation, stale evidence and failed replies retain original cleanup ownership. Existing retained-inode cleanup and legacy cwd spelling guards remain in force. Creation policy, directory ACL inheritance, raw symbolic targets and two-parent link/rename belong to the complete implementation. Plain ext2 durability, FAT lifetime and legacy cwd migration remain required. Tests will be authored; execution and CI observation remain deferred. ### Conditional journaled ext namespace serving — 1 October 2026 Every legacy and native namespace mutation attempt advances a nonwrapping mount epoch, rejecting remove/relink substitutions even when the inode is unchanged. Entry rows cannot grant content, navigation or ordinary metadata mutation. Native internal names use ext's 255-byte limit; legacy 240-byte reply rows refuse unrepresentable names without truncation. They cover original custody and permissions, short/lost replies, binding substitution, all effects, cross-mount refusal, retained content/parents, inherited local/external/streamed ACLs, full names/raw targets, allocation/epoch exhaustion, extended directory counts and uncertain publication. Full provider/lifetime acceptance remains open. Plain ext2 durable transactions, FAT namespace/lifetime and legacy cwd migration remain unfinished; spelling guards stay until their consumers migrate. Filesystem fsync/device-barrier ordering and both full guest EriX generations and external Rust/LLVM rebuilding remain required and unperformed. ### Design: explicitly selected original undo for plain ext2 Plain ext2 will retain its filesystem format and use the already configured same-disk external-journal partition as a separately formatted undo store. An immutable, checksummed footer binds the original filesystem UUID and both partition geometries. Neither discovery, formatting, a fallback journal nor an on-media identifier can grant another block route. The selected original journal is recovered before ordinary filesystem parsing. Read-only mounts cannot repair active media. A private joined block view exposes exactly the held filesystem extent and the selected journal extent to LibBlock’s existing undo owner. Ordinary callbacks receive only the filesystem prefix. Persistence barriers cover both original routes; target effects become durable before the journal is cleared. Semantic refusal rolls back; uncertainty permanently disables ordinary endpoint use. Mount-time repairs must use the same transaction owner, without nested recovery or an ambient bypass. Shared ext namespace, timestamp and detached-inode transactions will use this owner on admitted plain media. Original content owners and persistent orphan reclamation retain their existing lifetime rules. Authored controls will cover geometry/UUID substitution, unsupported durability, read-only recovery, rollback, lost completion, original ownership and all namespace effects. Integration will explicitly format/select the fixture partition and add VM scenarios. Documentation will specify the independent on-media format. Tests, builds and CI observation remain deferred by instruction. ### Original durable undo for plain ext — 1 October 2026 Runtime mounts never discover, format or replace a journal. Read-only mounts cannot repair active media; semantic refusal rolls back, while uncertain publication permanently disables ordinary endpoint use. Unselected plain media still refuse effects requiring rollback. Full namespace/lifetime parents, FAT serving, legacy cwd migration, complete filesystem fsync/JBD2 barriers and both full EriX guest generations plus guest Rust/LLVM rebuilding remain unfinished. ### Retire legacy provider pathname and spelling-pin adapters Current contextual consumers use independently retained native anchors, conditional component/fixed-entry acquisition and source-free retained effects. The older provider cwd-open, whole-target readlink and path-selected exact-entry families now remain in provider dispatch, compatibility adapters and tests. Inventory every opcode, codec and direct caller before deleting its producer. Retire cwd component open (0x639), its whole-target link observation (0x63A), and the obsolete path-selected fixed-entry acquisition/effect adapters where all ordinary consumers have migrated. Old operation numbers remain unassigned and must refuse without fallback. Keep actual native metadata, raw link pages, conditional namespace effects, retained entry effects, original anchors and acquisition-key retirement. Do not remove ordinary namespace/file interfaces that still have real users, including generic provider readdir. Remove cwd spelling-pin fields and their move/unlink guards only after the corresponding creation paths and dependent tests migrate. Remove legacy exact binding/parent spelling guards with their final acquisition producers. Preserve original object, parent and navigation-ceiling ownership; empty directory moves and detachment must retain actual held objects without pathname reopening or reuse. Conditional entry freshness, stale-binding refusal, original one-use effect semantics, permission evidence and positive cleanup remain mandatory. Imported filesystem-format limits remain explicit and are not bypassed. Migrate controls to actual native root/anchor/component/fixed-entry acquisition with original keys known before submission. Do not emulate removed APIs with test-only path reopeners, fabricated handles, copied identity or renamed legacy production code. Preserve independent identity/mount separation, maximal ID and capacity refusal, raw link lifetime, moved/detached ancestors, wrong handle kind, stale selection/replacement, timestamps, media recovery and cleanup ordering. Retain literal rejection controls for retired operation numbers. Share cohesive fixture helpers where useful; all authored code stays below 1,000 lines. Work through RAM, ext and FAT producers and dependent controls, then remove the unused shared codecs/IDs and remaining Vfsd adapter references. Publish signed checkpoints regularly and coordinate adopting immutable dependency revisions. Update component contracts and authored manual/API addenda. Tests/builds/checks, generated references, VM/profiler execution and CI observation remain deferred. Runtime catalogs and both compiled Rootd helper selections remain unchanged until coherent runtime adoption; full guest EriX and Rust/LLVM rebuilding remains required. Partial provider retirement does not close the complete lifetime item. Tracking: [codec audit](https://git.erikinkinen.fi/erix/lib-ipc/issues/1), [RAM audit](https://git.erikinkinen.fi/erix/ramfsd/issues/1), [ext audit](https://git.erikinkinen.fi/erix/e2fsd/issues/1), [FAT audit](https://git.erikinkinen.fi/erix/fatd/issues/1), [native ownership](https://git.erikinkinen.fi/erix/vfsd/issues/16), [Phase 6 tracker](https://git.erikinkinen.fi/erix/integration/issues/65). Ordinary V2 response correlation no longer admits retired effect operations. They retain root/parent/key fields, full-width handles and timestamps, optional trusted time, explicit selected fields, invalid destination refusal and untouched short outputs. New literal stat controls cover framing, canaries and retired-family refusal. Retired numeric replies cannot satisfy ordinary V2 or native effect correlation. Vfsd's last old exported-name references become literal timestamp-adapter refusals for all thirteen retired operations. The existing superseded-bridge/provider-spelling-pin acceptance criterion in [the native ownership feature](https://git.erikinkinen.fi/erix/vfsd/issues/16) is source-complete. Required imported FAT/exFAT binding and geometry guards remain. The remaining cwd/contextual-serving and complete lifecycle/control/graph criteria need a current-source acceptance audit and any missing implementation, followed by coherent runtime adoption. No synthetic weighted sub-item or full lifetime acceptance is added. Recomputed phase progress remains 18.95% weighted and 6.81% whole acceptance: 25/460 parents and 480/949 sub-items. Full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. </details> <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | docs | [issue 1](https://git.erikinkinen.fi/erix/docs/issues/1), [PR 4](https://git.erikinkinen.fi/erix/docs/pulls/4) | | docs.kernel.org | [inodes.html](https://docs.kernel.org/filesystems/ext4/inodes.html) | | e2fsd | [issue 17](https://git.erikinkinen.fi/erix/e2fsd/issues/17), [PR 3](https://git.erikinkinen.fi/erix/e2fsd/pulls/3), [conditional-namespace.md](https://git.erikinkinen.fi/erix/e2fsd/src/branch/feature/posix-compat/docs/conditional-namespace.md), [detached-inodes.md](https://git.erikinkinen.fi/erix/e2fsd/src/branch/feature/posix-compat/docs/detached-inodes.md), [original-undo.md](https://git.erikinkinen.fi/erix/e2fsd/src/branch/feature/posix-compat/docs/original-undo.md) | | fatd | [PR 3](https://git.erikinkinen.fi/erix/fatd/pulls/3) | | integration | [issue 102](https://git.erikinkinen.fi/erix/integration/issues/102), [issue 2](https://git.erikinkinen.fi/erix/integration/issues/2), [PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12), [ext-undo.md](https://git.erikinkinen.fi/erix/integration/src/branch/feature/posix-compat/docs/ext-undo.md) | | kernel | [issue 20](https://git.erikinkinen.fi/erix/kernel/issues/20) | | lib-ipc | [PR 2](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2), [conditional-namespace.md](https://git.erikinkinen.fi/erix/lib-ipc/src/branch/feature/posix-compat/docs/conditional-namespace.md), [retained-exact-entries.md](https://git.erikinkinen.fi/erix/lib-ipc/src/branch/feature/posix-compat/docs/retained-exact-entries.md) | | posixd | [PR 5](https://git.erikinkinen.fi/erix/posixd/pulls/5), [namespace-mutations.md](https://git.erikinkinen.fi/erix/posixd/src/branch/feature/posix-compat/docs/namespace-mutations.md) | | ramfsd | [PR 2](https://git.erikinkinen.fi/erix/ramfsd/pulls/2), [PR 3](https://git.erikinkinen.fi/erix/ramfsd/pulls/3) | | rootd | [PR 2](https://git.erikinkinen.fi/erix/rootd/pulls/2) | | vfsd | [PR 3](https://git.erikinkinen.fi/erix/vfsd/pulls/3) | </details>
erikinkinen changed title from [FEATURE] [P02.R16] Audit authority, code quality and documentation in e2fsd to [FEATURE] Audit authority, code quality and documentation in e2fsd 2026-09-12 08:02:17 +02:00
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:45 +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/e2fsd#1
No description provided.