[BUG] Attribute value quota charges are lost or counted under the wrong owner #11
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#11
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
Original ext file growth and truncation recompute charged sectors from the data map and can discard immutable attribute-value charges. Quota scans also count physical value inodes as ordinary identity-bearing files, rather than accounting modern shared values per referencing owner. A later write or ownership change can therefore produce inconsistent persistent usage.
Reproduction
Use admitted ext media with a modern EA-inode attribute value and a regular file. Grow and then truncate the file through its original retained provider handle; compare its charged sectors and quota usage before and after. Also compare ownership changes while two descriptors share the same value. Source inspection establishes these paths; no runtime reproduction, image or host test has been executed.
Expected and actual behavior
Expected: preserve cluster-rounded modern value charges alongside data/mapping/external-table storage. Charge every modern descriptor's owner for its full value and inode quota, without independently charging the shared physical inode. Retain the legacy owner-bound value's original quota identities. Distinguish attribute charges from symlink data allocation during read and cleanup.
Actual: the data-map accounting helper omits value charges, the legacy truncation branch can also omit external-table storage, inline metadata writers set sectors to zero, and the quota scanner counts each physical inode once. The resulting usage depends on storage sharing and later data-map operations. Inline conversion also retained its old payload in scratch that quota traversal reused before payload publication; the correction persists those original bytes before that reuse, within the same transaction. 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 covers media/quota.rs, mutation/extents.rs, file_io.rs, truncate.rs, inline_ops.rs, and symlink data selection. The correction belongs to the same persistent permission pass as ACL-aware mode changes. New accounting, identity-transfer and data-map controls are authored without execution under the user testing waiver.
Tracking
Continue within ext permission coherence and the mode/ACL correction. Reviews: provider, manual, Integration, and phase completion.
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