[FEATURE] Complete ext value-inode ACLs and persistent permission coherence #8
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/e2fsd#8
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
Native directory-access mediation consumes complete provider permission evidence. This pass addresses the ext provider's previously incomplete value-inode ACL acquisition, persistent mode coherence and shared value lifetimes. Those media paths and their bounded native metadata scenario are now implemented. Dedicated compatibility file-operation grants and conditional native mediation remain tracked in the broader permission feature.
Proposed behavior and scope
Complete the provider's value-inode acquisition, ACL-aware persistent metadata mutation and associated lifetime handling as one coherent pass. Preserve the original admitted mount, retained inode/handle identity, complete-table validation, native operation ceilings and conditional-effect revision contracts.
Stream selected value-inode bytes through explicit existing format-sized provider scratch. Validate the original EA feature/role, complete inode checksums and size, format-defined content integrity and original references before publishing metadata or ACL pages. Use complete canonical ACL validation without a new small entry-count or value-size cap. Keep both attribute stores visible and reject duplicates or malformed suffixes. No byte prefix can establish permission, and no failed acquisition may become ACL absence.
Make persistent mode changes update the ACL's owner, group/mask and other classes coherently while preserving named entries and default ACLs. Preserve shared attribute blocks, same-range values and shared value inodes through copy-on-write as required by the format. Keep full owner IDs and special-mode rules explicit. Apply existing journal/transaction, read-only, immutability, checksum and quota contracts; refuse real resource exhaustion before exposing an inconsistent result. Permission observations must invalidate before attempted metadata effects, and conditional operations must still check original fresh evidence.
Retire inline and external attribute references under their format-defined lifetimes. Decrement shared value references and free storage only on the final reference, without traversing an arbitrary ordinary file as an attribute object. Preserve cleanup after partial failures and avoid replaying an uncertain effect. Do not expose native capabilities, device selection or private inode selectors to compatibility clients.
Authority, security and reliability
The private provider endpoint and already admitted mount/retained handle select authority. IDs, checksums, ACL classes and paths are descriptive only. All selected media must remain within that original device and object scope. Metadata cannot widen a native ceiling or revive a retired permission revision. Keep source, recipient, object, rights, lifetime, sharing and disposal explicit for each new helper. Never bypass malformed evidence or remove a correctness gate to speed acquisition.
Use independently authored code derived from ext format documentation and existing EriX contracts. Do not copy or translate external implementations. Reuse canonical parsers, bounded scratch and mutation primitives; split thematic files below one thousand lines and retain rustdoc/missing_docs enforcement.
Acceptance criteria
Checklist
Alternatives and tradeoffs
Refusing all value-inode ACLs is an existing implementation gap, not the intended final supported behavior. Treating unknown evidence as absent is unacceptable. Copying a complete arbitrary-length ACL into a fixed array would add a hidden limit. Modifying shared attribute storage in place could change another inode's permission data. Streaming, exact sharing accounting and format-aware copy-on-write preserve the original object and native boundary while allowing complete valid input.
Tracking and rollout
Native ACL metadata coverage — 29 September 2026: integration
e9dbf028, e2fsdcc3d02a0, docs829c91a8, rootd93e2d63b.The dedicated scenario uses a separate ext4 image and Rootd's existing explicitly writable VFS fixture. Twenty-five original native requests cover local/value ACL mode and full-owner changes, owner-only preservation, rejected type changes with unchanged metadata, special bits, an untouched peer, deletion and definite second-unlink absence. A directory retains its original default ACL. No new capability, realm binding, provider selector or production policy is added.
Independent post-VM host decoding compares every access/default ACL entry, unrelated attributes and original payloads, confirms local/value storage, and retains the mandatory read-only e2fsck step. The constructor proves actual storage kinds before boot; 512 named entries are fixture geometry, not a provider limit. Bounded host reads avoid copying a complete disk. Five Rust orchestration controls and seven Python oracle controls are authored and unrun. Rustfmt was applied; changed source stays below one thousand lines. A read-only inventory covers 76 repositories and 3359 source files; none reaches that threshold.
The provider acquisition/mutation/lifetime scope, including its native scenario authoring, is implemented and is accepted under the testing waiver. Four repositories are published in five signed commits. Rootd's two Cargo selectors and both independent helper catalog selectors select the original helper
5284c4a6; seven catalog edges adopt that helper, its consumer and maintained contracts. The later catalog-only head is distinct. Related reviews: Integration, Rootd, provider, manual.No fixture generation, tests, builds, lint checks, Rustdoc generation, VM/manual/profiler runs or CI observation were executed. No pass, warning-free build, measured speedup or guest-build result is claimed. Native conditional mediation remains open: current realm directory-metadata/byte-stream bindings must not be broadened into file-mutation grants. Dedicated operation authority and conditional effects remain implementation work. Both full EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished.
Fresh checklist arithmetic remains 16.23% weighted, 4.81% whole-item, 20/460 parents and 437/897 sub-items. This completes coverage within an already accepted provider sub-item and adds no duplicate runtime-feature credit.
Persistent ACL metadata checkpoint — 29 September 2026: e2fsd
ac258003, docs2d3de8f0, integrationcd4f7625.The original ext metadata operation now preflights all selected fields and complete access ACLs, changes only owner/group-or-mask/other permissions, and preserves named/default entries and full-width owner IDs. Shared tables and immutable values use copy-on-write with exact reference lifetimes. Local alias pressure uses actual table geometry, the other attribute store or value-inode storage. Root metadata follows the original native scope; the full nonzero table reference domain has no separate 1024-owner ceiling. The incompatible Hurd/EA count-word layout refuses during mount parsing.
Mode/ACL coherence and attribute accounting are implemented. Modern charges follow every descriptor's owner; legacy values retain original independent quota identities. Growth, truncation and inline conversion conserve charges, fast symlinks distinguish attributes from data, and retained inline payload is persisted before quota scanning reuses its scratch. Every edit retains the original transaction, checksums and permission epoch. Uncertain persistent completion remains fail-stop without replay. No capability, endpoint or private inode-selector ABI is added.
Twenty-four new controls are authored and unrun, covering actual media/provider metadata, sharing, full IDs, root, both storage-movement directions, large immutable ACLs, count/space exhaustion, quota identity/cluster charges, real quota-file inline conversion, growth/truncation, fast symlinks, journal rollback and uncertain writes. Rustfmt was applied. Changed Rust source remains below one thousand lines (maximum 922), with inline rustdoc and missing_docs retained. A read-only inventory covers 76 repositories and 3355 tracked source files; none reaches one thousand lines. Duplicate raw quota decoding was removed and directory allocation I/O was moved into its existing module.
The provider permission pass continues with operation-specific conditional native effects and native scenario authoring. Native filesystem mediation, both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished. The checklist now exposes the completed provider media portion separately; recalculation is 16.23% weighted, 4.81% whole-item, 20/460 parents and 437/897 sub-items. The weighted percentage still rounds to 16.23%; it has been recalculated. Reviews: provider, manual, Integration.
Ext value-inode acquisition and cleanup checkpoint — 29 September 2026: e2fsd
407efa3e, docs6d5da74b, integration328c153f.The original provider now streams complete access ACLs from local and EA-inode storage with exact size/role, original inode checksums, modern CRC32C binding or legacy owner/generation validation. One cached data block and fixed owned scratch admit large ACLs without a new total-size or entry-count cap. Failed or changed evidence clears staged pages and retires the matching original observation. No capability, endpoint or credential authority is added.
Shared and inline cleanup is implemented: both stores are preflighted, repeated references cannot undercount the original value, shared external tables retain their own value references, and only a final value reference disposes storage. Raw hash/count fields are distinct from timestamps, EA-only inodes refuse ordinary file selection, and uncertain nonjournaled writes retain provider fail-stop without replay. Seventeen new media/provider controls are authored and unrun, including actual retained dispatch and ACLs above 64 KiB/8191 entries.
The provider permission pass remains open for ACL-aware persistent mode changes and the remaining operation-specific effects. Native filesystem mediation, both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished. Canonical phase completion remains 16.23% weighted, 4.81% whole-item, 20/460 parents and 436/896 sub-items; no new small canonical completion item is added for this checkpoint. Reviews: provider, manual, Integration.
Continues native permission enforcement, original directory access and retained ext permission evidence. Coordinate provider review, Vfsd review, Integration review, manual review and phase completion. Full pathname/open/stat/mutation mediation and the required EriX/Rust/LLVM guest rebuilds remain unfinished.
erikinkinen referenced this issue2026-09-29 14:07:01 +02:00
erikinkinen referenced this issue from erix/docs2026-09-29 14:17:05 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 14:17:06 +02:00
erikinkinen referenced this issue from erix/rootd2026-09-29 15:37:16 +02:00