[BUG] Filesystem permission and extent controls retain invalid names and ownership APIs #20
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#20
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
Stale permission and extent fixtures fail strict compilation, including indexing a consumed noncopyable handle reservation.
Reproduction
Run the repository CI workflow against the original source.
Expected and actual behavior
The existing controls should compile without changing inode formats, identity widths or ownership. Malformed error identifiers, stale module/import paths, ambiguous device words and old reservation/extent APIs prevent them from running.
Environment and identity
Evidence and prior checks
Keep the original assertions and failure results while updating the actual interfaces. Fixture-owned writable media must be explicit; the empty production mount remains read-only.
Tracking
Fixes are included in #44.