[BUG] exFAT producers omit the mandatory stream allocation flag #10

Closed
opened 2026-10-01 01:21:35 +02:00 by erikinkinen · 0 comments
Owner

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:

  1. Use Fatd to create a file or directory on writable exFAT media.
  2. Inspect the second entry of the new file set, the Stream Extension.
  3. Read bit 0 of its GeneralSecondaryFlags byte at offset 1.
  4. Compare with the independent format requirement in section 7.6.2.1.

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

  • Fatd baseline: e402563f7f1f33adf7a976ee7214cb440f7a563c.
  • Integration baseline: 433f0f5479e325438ad6a668dfdea054f9366406.
  • Configuration: writable exFAT and generated exFAT fixtures.
  • Image digest, hardware/VM, architecture and toolchain: no execution was performed.
  • Route: existing explicitly mounted device and private provider operation; no new authority is required.
  • Last known working revision: unknown.

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

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
Repository Links
docs PR 4
fatd issue 10, exfat-directory-mutation.md, original-catalog.md
posixd issue 25, PR 5
rootd PR 2
## 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: 1. Use Fatd to create a file or directory on writable exFAT media. 2. Inspect the second entry of the new file set, the Stream Extension. 3. Read bit 0 of its GeneralSecondaryFlags byte at offset 1. 4. Compare with the independent format requirement in section 7.6.2.1. 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 - Fatd baseline: `e402563f7f1f33adf7a976ee7214cb440f7a563c`. - Integration baseline: `433f0f5479e325438ad6a668dfdea054f9366406`. - Configuration: writable exFAT and generated exFAT fixtures. - Image digest, hardware/VM, architecture and toolchain: no execution was performed. - Route: existing explicitly mounted device and private provider operation; no new authority is required. - Last known working revision: unknown. ## Evidence and prior checks [The exFAT specification](https://learn.microsoft.com/en-us/windows/win32/fileio/exfat-specification#7621-allocationpossible-field) defines the required flag. The source finding concerns [Fatd creation](https://git.erikinkinen.fi/erix/fatd/src/commit/e402563f7f1f33adf7a976ee7214cb440f7a563c/src/exfat.rs) and the [independent fixture encoder](https://git.erikinkinen.fi/erix/integration/src/commit/433f0f5479e325438ad6a668dfdea054f9366406/scripts/exfat_variants.py). 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](https://git.erikinkinen.fi/erix/fatd/issues/8) - [Directory-growth repair](https://git.erikinkinen.fi/erix/fatd/issues/9) - [Fatd review](https://git.erikinkinen.fi/erix/fatd/pulls/3) - [Integration review](https://git.erikinkinen.fi/erix/integration/pulls/12) - [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65) - [x] Correct the runtime and independent fixture producers. - [x] Require the mandatory bit during media admission and post-image verification. - [x] 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. <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | docs | [PR 4](https://git.erikinkinen.fi/erix/docs/pulls/4) | | fatd | [issue 10](https://git.erikinkinen.fi/erix/fatd/issues/10), [exfat-directory-mutation.md](https://git.erikinkinen.fi/erix/fatd/src/branch/feature/posix-compat/docs/exfat-directory-mutation.md), [original-catalog.md](https://git.erikinkinen.fi/erix/fatd/src/branch/feature/posix-compat/docs/original-catalog.md) | | posixd | [issue 25](https://git.erikinkinen.fi/erix/posixd/issues/25), [PR 5](https://git.erikinkinen.fi/erix/posixd/pulls/5) | | rootd | [PR 2](https://git.erikinkinen.fi/erix/rootd/pulls/2) | </details>
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:00 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/fatd#10
No description provided.