[BUG] exFAT directory growth leaves new entries beyond the recorded length #9
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/fatd#9
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
Creating or renaming an entry into a full non-root exFAT directory can extend its
allocation without updating its stored stream length. The resulting entry can be
outside the range used by subsequent lookup and directory enumeration.
Reproduction
Source-derived reproduction, not an executed VM or unit-test result:
The same boundary can be reached by rename. Contiguous directories additionally
encounter an unconditional refusal instead of conversion to a FAT chain.
Reproduction frequency and clean-image runtime behavior have not been measured.
Expected and actual behavior
Expected: allocation, initialized length, data length and allocation flags are
published together through the retained original directory entry. Existing held
directory and child descriptions observe the new geometry. Selected original
metadata commits or rolls back with the filesystem mutation.
Source finding: free-slot allocation appends directory clusters, but its caller
retains only
DirNode, without the original owner entry needed to publish thelength. Writes do not check that length; reads do. No executed error/output is
claimed.
Environment and identity
e402563f7f1f33adf7a976ee7214cb440f7a563c.433f0f5479e325438ad6a668dfdea054f9366406.Evidence and prior checks
The affected baseline is directory allocation and entry I/O.
Source review traces the mismatch between free-slot growth and counted directory
reads. Regression controls are being authored for creation, rename, contiguous
conversion, held aliases, zero-length directories, rollback and remount.
Test/build execution and CI observation are waived by the maintainer for now.
Tracking
Original FAT-family metadata
Fatd implementation review
Phase 6 completion
Retain the original parent entry and publish directory geometry with allocation.
Refresh held parent/child geometry and preserve selected-catalog rollback.
Author independent positive, malformed-input and rollback controls; update contracts and publish coherent revisions.
Complete original metadata and status/directory source acceptance — 1 October 2026
Source acceptance covers explicit format admission/recovery, persistent original identities and full metadata, shared ordinary/acquired observations, fresh permissions, atomic filesystem/catalog updates, alias and cleanup lifetime, compatibility stat families and shared seekable directory descriptions. Imported unavailable facts remain explicit refusals.
Runtime and independent fixture producers emit the mandatory stream allocation flag, which admission and image verification require.
This checkpoint authors 14 Rust and four Python controls plus two selected exFAT VM scenarios; two existing FAT scenarios now also require six-child directory growth, post-growth observations and complete cleanup.
Both complete EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed.
Related records and contracts
erikinkinen referenced this issue from erix/docs2026-10-01 01:41:00 +02:00
erikinkinen referenced this issue2026-10-01 01:41:01 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 01:41:02 +02:00
erikinkinen referenced this issue from erix/posixd2026-10-01 01:41:03 +02:00
erikinkinen referenced this issue from erix/rootd2026-10-01 01:41:04 +02:00