[BUG] Valid exFAT upcase table is rejected at U+FFFF #17

Open
opened 2026-10-18 14:41:10 +02:00 by erikinkinen · 1 comment
Owner

Summary

Fatd rejects a valid exFAT upcase table whose final word maps U+FFFF to itself. This includes the recommended table produced by mkfs.exfat, so ordinary mount admission fails.

Reproduction

Format the existing Integration 64 MiB regular-file fixture with mkfs.exfat -L ERIXLIVE. Its 5,836-byte upcase table has checksum E619D30D and ends with literal FFFF.

An independent smaller table contains the mandatory first 128 mappings followed by FFFF FF7F FFFF. The counted identity run ends at U+FFFE; the final word supplies the remaining mapping.

Expected and actual behavior

Mount admission and filename conversion should accept the complete table. The original parser treats the final FFFF as another compression marker, demands a nonexistent count and returns INVALID_ARGUMENT. Interior markers and malformed runs must retain their existing checks.

Environment and identity

  • Fatd: 084143d1f9ae6406d909240fdbf50e5d4da66d3e.
  • Integration: 6f20e691142054bfae65eaf52d0fa5c3788879f8; x86-64, one CPU, release image with development runtime.
  • Guest case: appliance-disk-image-realm-filesystem-exfat-positive.
  • Host formatter: exfatprogs 1.4.3; original catalog and undo journal retained.
  • Existing filesystem and block capabilities suffice; no additional authority is needed.
  • Last working revision: not established.

Evidence and prior checks

Integration CI 2870 exits 41 instead of 33 before storage readiness. That coarse guest outcome does not identify a parser step. Separately, compiled controls against the original parser reproduce both final-literal refusals, while three companion controls pass.

The exFAT specification, section 7.2.5.1 specifies the recommended table and checksum. The repair covers that table and independently authored boundary cases; exact-source guest acceptance remains open.

Tracking

  • Distinguish the final literal from interior compression markers in admission and lookup.
  • Preserve checksum, malformed-run, range and allocation refusals.
  • Pass independent boundary and recommended-table provider controls.
  • Pass the original guest workload on the repaired source graph.

Implementation: PR #3. Phase scope: Integration #65.

## Summary Fatd rejects a valid exFAT upcase table whose final word maps `U+FFFF` to itself. This includes the recommended table produced by `mkfs.exfat`, so ordinary mount admission fails. ## Reproduction Format the existing Integration 64 MiB regular-file fixture with `mkfs.exfat -L ERIXLIVE`. Its 5,836-byte upcase table has checksum `E619D30D` and ends with literal `FFFF`. An independent smaller table contains the mandatory first 128 mappings followed by `FFFF FF7F FFFF`. The counted identity run ends at `U+FFFE`; the final word supplies the remaining mapping. ## Expected and actual behavior Mount admission and filename conversion should accept the complete table. The original parser treats the final `FFFF` as another compression marker, demands a nonexistent count and returns `INVALID_ARGUMENT`. Interior markers and malformed runs must retain their existing checks. ## Environment and identity - Fatd: `084143d1f9ae6406d909240fdbf50e5d4da66d3e`. - Integration: `6f20e691142054bfae65eaf52d0fa5c3788879f8`; x86-64, one CPU, release image with development runtime. - Guest case: `appliance-disk-image-realm-filesystem-exfat-positive`. - Host formatter: `exfatprogs 1.4.3`; original catalog and undo journal retained. - Existing filesystem and block capabilities suffice; no additional authority is needed. - Last working revision: not established. ## Evidence and prior checks [Integration CI 2870](https://git.erikinkinen.fi/erix/integration/actions/runs/2870) exits 41 instead of 33 before storage readiness. That coarse guest outcome does not identify a parser step. Separately, compiled controls against the original parser reproduce both final-literal refusals, while three companion controls pass. [The exFAT specification, section 7.2.5.1](https://learn.microsoft.com/en-us/windows/win32/fileio/exfat-specification#7251-recommended-up-case-table) specifies the recommended table and checksum. The repair covers that table and independently authored boundary cases; exact-source guest acceptance remains open. ## Tracking - [x] Distinguish the final literal from interior compression markers in admission and lookup. - [x] Preserve checksum, malformed-run, range and allocation refusals. - [x] Pass independent boundary and recommended-table provider controls. - [ ] Pass the original guest workload on the repaired source graph. Implementation: [PR #3](https://git.erikinkinen.fi/erix/fatd/pulls/3). Phase scope: [Integration #65](https://git.erikinkinen.fi/erix/integration/issues/65).
Author
Owner

The repair is published in 3a4b046c, and Integration 30580361 selects it in both catalogs. The original parser reproduces both valid-table refusals; the repaired provider passes all five boundary/table controls and the complete local matrix. Source and local criteria are checked. The original guest workload remains open.

The repair is published in [3a4b046c](https://git.erikinkinen.fi/erix/fatd/commit/3a4b046c750363aa1d57feea2d6e43f9ffba8cea), and [Integration 30580361](https://git.erikinkinen.fi/erix/integration/commit/305803617d2b23995e314abfafce797e81e19036) selects it in both catalogs. The original parser reproduces both valid-table refusals; the repaired provider passes all five boundary/table controls and the complete local matrix. Source and local criteria are checked. The original guest workload remains open.
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#17
No description provided.