[BUG] exFAT producers omit the mandatory stream allocation flag #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/fatd#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
Newly created exFAT file and directory stream extensions omit the mandatory
AllocationPossible bit. Integration's exFAT fixture encoder used the same
incorrect encoding, so those fixtures did not distinguish it from valid media.
Reproduction
Source-derived reproduction; no test or image was executed:
The same missing bit is visible in the Integration fixture encoder's default
stream flags. Runtime frequency and behavior with external filesystem tools
have not been observed.
Expected and actual behavior
Expected: every file/directory Stream Extension sets AllocationPossible. The
NoFatChain bit independently describes contiguous allocation. Admission and the
independent image verifier reject streams missing the required bit.
Actual source: Fatd initializes stream flags to zero, the fixture encoder writes
its zero default unchanged, and admission checks only for unknown flag bits.
Environment and identity
e402563f7f1f33adf7a976ee7214cb440f7a563c.433f0f5479e325438ad6a668dfdea054f9366406.Evidence and prior checks
The exFAT specification
defines the required flag. The source finding concerns
Fatd creation
and the independent fixture encoder.
Positive chained/contiguous producer checks and malformed-flag controls are
authored and unrun. Test/build execution and CI observation are waived by the
maintainer for now.
Tracking
Original FAT-family metadata
Directory-growth repair
Fatd review
Integration review
Phase 6 completion
Correct the runtime and independent fixture producers.
Require the mandatory bit during media admission and post-image verification.
Author regression controls and publish the coherent provider/fixture 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