[BUG] Host exFAT verifier misreads the final upcase mapping #168

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

Summary

The host exFAT image observer misreads a final literal U+FFFF mapping as an interior compression marker. It rejects valid complete tables, including the recommended format table, and can consume an extra word as a run count after that final mapping.

Reproduction

At Integration e38c9571f3ee77100297c9f54b298a283359c7d9, call parse_upcase_table in scripts/verify-exfat-image.py with the required 128-entry ASCII uppercase prefix followed by the little-endian words FFFF FF7F FFFF. An independent fully literal table ending in FFFF gives the same refusal.

The direct controls are maintained in tests/exfat_upcase_table_test.py in the repair. They author format words independently and do not require an external implementation or table fixture.

Expected and actual behavior

U+FFFF must retain its final literal mapping. Earlier FFFF words remain counted identity-run markers, and words after a complete table must be rejected.

The original decoder raises ValueError: truncated exFAT upcase run for both valid final-literal encodings. It accepts a suffix containing an extra 0001 after the complete final mapping. The repaired direct controls preserve refusal of odd, truncated, zero-run and overflowing inputs.

Environment and identity

  • Affected published Integration source: e38c9571f3ee77100297c9f54b298a283359c7d9.
  • Host-only Python observer; no guest or runtime authority changes.
  • Normative format: Microsoft exFAT specification, section 7.2.5.1.

Evidence and prior checks

The retained local reproductions use test/decoder bytes identical to this published source.

Original direct-test streams retain two valid-table errors and the excess-word acceptance. The corrected decoder passes all four direct controls and the affected fixture/observer modules. The larger-cluster VM fixture uses an existing short compressed table and did not require this repair to be parsed.

Tracking

  • Distinguish the final literal from interior run markers in the host observer.
  • Preserve direct positive and malformed-input controls.
  • Pass current-source Integration CI.

Related native-parser defect: Fatd #17. Format reference: Microsoft exFAT specification.

Implementation: PR #12. Phase scope: #65.

## Summary The host exFAT image observer misreads a final literal U+FFFF mapping as an interior compression marker. It rejects valid complete tables, including the recommended format table, and can consume an extra word as a run count after that final mapping. ## Reproduction At Integration `e38c9571f3ee77100297c9f54b298a283359c7d9`, call `parse_upcase_table` in `scripts/verify-exfat-image.py` with the required 128-entry ASCII uppercase prefix followed by the little-endian words `FFFF FF7F FFFF`. An independent fully literal table ending in `FFFF` gives the same refusal. The direct controls are maintained in `tests/exfat_upcase_table_test.py` in the repair. They author format words independently and do not require an external implementation or table fixture. ## Expected and actual behavior U+FFFF must retain its final literal mapping. Earlier FFFF words remain counted identity-run markers, and words after a complete table must be rejected. The original decoder raises `ValueError: truncated exFAT upcase run` for both valid final-literal encodings. It accepts a suffix containing an extra `0001` after the complete final mapping. The repaired direct controls preserve refusal of odd, truncated, zero-run and overflowing inputs. ## Environment and identity - Affected published Integration source: `e38c9571f3ee77100297c9f54b298a283359c7d9`. - Host-only Python observer; no guest or runtime authority changes. - Normative format: Microsoft exFAT specification, section 7.2.5.1. ## Evidence and prior checks The retained local reproductions use test/decoder bytes identical to this published source. Original direct-test streams retain two valid-table errors and the excess-word acceptance. The corrected decoder passes all four direct controls and the affected fixture/observer modules. The larger-cluster VM fixture uses an existing short compressed table and did not require this repair to be parsed. ## Tracking - [x] Distinguish the final literal from interior run markers in the host observer. - [x] Preserve direct positive and malformed-input controls. - [ ] Pass current-source Integration CI. Related native-parser defect: [Fatd #17](https://git.erikinkinen.fi/erix/fatd/issues/17). Format reference: [Microsoft exFAT specification](https://learn.microsoft.com/en-us/windows/win32/fileio/exfat-specification#7251-recommended-up-case-table). Implementation: [PR #12](https://git.erikinkinen.fi/erix/integration/pulls/12). Phase scope: [#65](https://git.erikinkinen.fi/erix/integration/issues/65).
Author
Owner

Fixed in 7d3e7b3f. The host decoder accepts the final U+FFFF literal after the preceding 65,535 mappings, while interior U+FFFF entries still introduce compressed runs. Malformed and excess mappings remain rejected. The current-source CI criterion remains open.

Fixed in [7d3e7b3f](https://git.erikinkinen.fi/erix/integration/commit/7d3e7b3f845d1fea372a4f682126ccb3c3b9496b). The host decoder accepts the final U+FFFF literal after the preceding 65,535 mappings, while interior U+FFFF entries still introduce compressed runs. Malformed and excess mappings remain rejected. The current-source CI criterion remains open.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:20 +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/integration#168
No description provided.