[BUG] Mode updates leave persistent access ACLs inconsistent #10
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#10
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?
Summary
The ext metadata setter writes mode bits without changing the corresponding access-ACL classes. On an inode with a valid access ACL, changing owner/group/other mode permissions can leave internally inconsistent persistent metadata. The complete permission reader then rejects that inode instead of returning usable evidence.
Reproduction
Create admitted ext media with a valid access ACL corresponding to mode 0750, then request a native metadata mode change to 0700 through the original authorized provider route. Read complete permission evidence from the same retained inode afterwards. Current source updates the mode field only, leaving the old group or mask permissions in the ACL. This report is source-confirmed; tests, images and VM runs were not executed.
Expected and actual behavior
Expected: update the owner, group-or-mask and other access-ACL permissions with the requested mode in the same original metadata operation. Preserve named entries, default ACLs, shared value ranges, shared external blocks and value-inode lifetimes through copy-on-write as needed. Retain native ceilings, metadata invalidation, checksums, quota accounting, journal rollback and uncertain-write handling.
Actual: apply_mode changes only the inode mode bytes. No ACL edit accompanies write_metadata_update. A subsequent complete ACL/mode comparison refuses the inconsistent result. No native authority escape is claimed.
Environment and identity
407efa3ea1.Evidence and prior checks
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.
Source review of media/metadata.rs and media/xattr/access_acl/decode.rs establishes the write and later refusal paths. The provider already invalidates permission observations before metadata attempts; this report concerns persistent mode/ACL coherence. Existing controls and new mutation controls will remain authored-but-unrun under the user testing waiver.
Tracking
Complete within ext permission coherence, with provider review, manual review, Integration review and phase completion. This continues the implemented value-inode acquisition and reference-lifetime work.
erikinkinen referenced this issue2026-09-29 15:08:28 +02:00
erikinkinen referenced this issue from erix/docs2026-09-29 15:08:28 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 15:08:29 +02:00