[BUG] Native EXT mutations impose an unintended UTF-8 basename restriction #21

Open
opened 2026-10-12 13:52:19 +02:00 by erikinkinen · 0 comments
Owner

Summary

Native ext mutations reject valid non-UTF-8 basenames before reaching the authorized operation.

Reproduction

At the original source, supply a 255-byte basename containing 0xff through a held parent on writable media. Creation, link, rename, removal and recovery paths can reach a text-only name validator.

Expected and actual behavior

Native basenames must preserve bytes within the ext name limit. Reject empty names, NUL, separators and navigation aliases without imposing UTF-8. Keep configured casefold/encryption behavior, administrative path rules and the original authority boundaries.

Environment and identity

  • x86-64 host filesystem controls and their selected public supplier graph.
  • Explicitly retained parent and operation; no extra device or namespace grant.
  • No guest-image result or known working revision has been established.

Evidence and prior checks

The raw native component rule and physical name bound must apply consistently across the shared mutation paths.

Tracking

Fixes and full-name regression coverage are included in #44.

## Summary Native ext mutations reject valid non-UTF-8 basenames before reaching the authorized operation. ## Reproduction At the [original source](https://git.erikinkinen.fi/erix/e2fsd/commit/626bcd7b9c63cfe3eca07036260cb1265164f8c0), supply a 255-byte basename containing `0xff` through a held parent on writable media. Creation, link, rename, removal and recovery paths can reach a text-only name validator. ## Expected and actual behavior Native basenames must preserve bytes within the ext name limit. Reject empty names, NUL, separators and navigation aliases without imposing UTF-8. Keep configured casefold/encryption behavior, administrative path rules and the original authority boundaries. ## Environment and identity - x86-64 host filesystem controls and their selected public supplier graph. - Explicitly retained parent and operation; no extra device or namespace grant. - No guest-image result or known working revision has been established. ## Evidence and prior checks The raw native component rule and physical name bound must apply consistently across the shared mutation paths. ## Tracking Fixes and full-name regression coverage are included in #44.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:47 +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/e2fsd#21
No description provided.