[BUG] FAT status invents timezone and change-time evidence #7

Closed
opened 2026-09-30 17:52:06 +02:00 by erikinkinen · 0 comments
Owner

Summary

FAT-family status invents timestamp evidence in two places: exFAT decodes an unavailable UTC offset as a known zero offset, and legacy status copies modification time into metadata-change time although neither format records POSIX ctime. Untimestamped exFAT creation also marks its calendar placeholder as known UTC.

Reproduction

At Fatd f30feafea342fa41f4d4ac5136190c3b644b0bbd, inspect utc_offset_seconds and new_for_node in src/exfat/metadata.rs, and StatResult::from_node in src/store.rs. A valid local calendar value with offset byte zero becomes a UTC timestamp. The legacy change-time result always copies the modification value. No clock or timezone evidence accompanies either conversion.

Original literal entry controls will distinguish valid UTC zero, positive and negative offsets, unavailable UTC and invalid encodings. Provider controls will observe the original retained entry, preserve media bytes and verify independent time availability. This is a source-derived reproduction; tests, builds, lint checks, VM/profiler execution and CI observation remain deferred by user instruction.

Expected and actual behavior

Expected: retain each timestamp's calendar value and actual UTC availability independently. FAT's offset-free calendar fields and exFAT's unavailable-offset form must not assert a UTC instant without explicit timezone policy. Known exFAT offsets yield recorded UTC observations with their real storage precision. Birth time and modification time must never supply ctime. Legacy replies use their documented unknown-zero representation for unavailable fields; the source-qualified interface uses explicit Unknown observations.

Actual: unavailable timezone evidence becomes a successful UTC interpretation, and ctime is inferred from mtime. New untimestamped exFAT entries advertise the placeholder as known UTC. Native source-qualified snapshots also discard valid independently available exFAT times.

Environment and identity

  • Fatd: f30feafea342fa41f4d4ac5136190c3b644b0bbd; Integration graph: 6299bffb7a69f46e87b7504651025b6b7c0f641b.
  • Input: original FAT/exFAT directory entries through retained native mount/handle custody.
  • Image, VM and toolchain: none executed for this source audit.
  • Authority: existing metadata observation and format updates; no additional clock, timezone, device or filesystem route.
  • Last known working revision: not established.

Evidence and prior checks

The source branches above directly select assumed UTC and copied ctime. The repair retains local values for format-preserving rename and metadata updates, while exposing only independently supported UTC observations. It uses original Rust implementation and independent entry literals; no external implementation code is imported. Format semantics follow the Microsoft exFAT specification.

Tracking

Related status and directory work, Fatd review and phase completion. Close after repair and coherent signed publication under the testing waiver. Complete FAT POSIX identity/ownership policy and pipe/stream status remain unfinished requirements.

Original FAT-family timestamp evidence — 30 September 2026

Unknown offset bits cannot invent UTC.

Full compatibility status still refuses incomplete required metadata.

Existing date quantization assertions and actual VM/image checks remain and now require truthful UTC availability.

The full status/directory feature remains open for complete FAT metadata, pipe/stream status and remaining full-item integration. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Related records and contracts
Repository Links
docs PR 4
fatd issue 7
integration PR 12
rootd PR 2
## Summary FAT-family status invents timestamp evidence in two places: exFAT decodes an unavailable UTC offset as a known zero offset, and legacy status copies modification time into metadata-change time although neither format records POSIX ctime. Untimestamped exFAT creation also marks its calendar placeholder as known UTC. ## Reproduction At Fatd `f30feafea342fa41f4d4ac5136190c3b644b0bbd`, inspect `utc_offset_seconds` and `new_for_node` in `src/exfat/metadata.rs`, and `StatResult::from_node` in `src/store.rs`. A valid local calendar value with offset byte zero becomes a UTC timestamp. The legacy change-time result always copies the modification value. No clock or timezone evidence accompanies either conversion. Original literal entry controls will distinguish valid UTC zero, positive and negative offsets, unavailable UTC and invalid encodings. Provider controls will observe the original retained entry, preserve media bytes and verify independent time availability. This is a source-derived reproduction; tests, builds, lint checks, VM/profiler execution and CI observation remain deferred by user instruction. ## Expected and actual behavior Expected: retain each timestamp's calendar value and actual UTC availability independently. FAT's offset-free calendar fields and exFAT's unavailable-offset form must not assert a UTC instant without explicit timezone policy. Known exFAT offsets yield recorded UTC observations with their real storage precision. Birth time and modification time must never supply ctime. Legacy replies use their documented unknown-zero representation for unavailable fields; the source-qualified interface uses explicit Unknown observations. Actual: unavailable timezone evidence becomes a successful UTC interpretation, and ctime is inferred from mtime. New untimestamped exFAT entries advertise the placeholder as known UTC. Native source-qualified snapshots also discard valid independently available exFAT times. ## Environment and identity - Fatd: `f30feafea342fa41f4d4ac5136190c3b644b0bbd`; Integration graph: `6299bffb7a69f46e87b7504651025b6b7c0f641b`. - Input: original FAT/exFAT directory entries through retained native mount/handle custody. - Image, VM and toolchain: none executed for this source audit. - Authority: existing metadata observation and format updates; no additional clock, timezone, device or filesystem route. - Last known working revision: not established. ## Evidence and prior checks The source branches above directly select assumed UTC and copied ctime. The repair retains local values for format-preserving rename and metadata updates, while exposing only independently supported UTC observations. It uses original Rust implementation and independent entry literals; no external implementation code is imported. Format semantics follow the [Microsoft exFAT specification](https://learn.microsoft.com/en-us/windows/win32/fileio/exfat-specification#7410-utcoffset-fields). ## Tracking Related [status and directory work](https://git.erikinkinen.fi/erix/posixd/issues/25), [Fatd review](https://git.erikinkinen.fi/erix/fatd/pulls/3) and [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). Close after repair and coherent signed publication under the testing waiver. Complete FAT POSIX identity/ownership policy and pipe/stream status remain unfinished requirements. ### Original FAT-family timestamp evidence — 30 September 2026 Unknown offset bits cannot invent UTC. Full compatibility status still refuses incomplete required metadata. Existing date quantization assertions and actual VM/image checks remain and now require truthful UTC availability. The [full status/directory feature](https://git.erikinkinen.fi/erix/posixd/issues/25) remains open for complete FAT metadata, pipe/stream status and remaining full-item integration. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX 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 7](https://git.erikinkinen.fi/erix/fatd/issues/7) | | integration | [PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12) | | rootd | [PR 2](https://git.erikinkinen.fi/erix/rootd/pulls/2) | </details>
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:59 +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#7
No description provided.