[BUG] Inode size and allocated-block metadata ignore format feature semantics #19
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/e2fsd#19
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Inode decoding treats huge-file allocation counts as sectors even when the inode flag selects filesystem blocks. Metadata writes can preserve that flag while encoding sector counts, and large-file growth omits required filesystem feature metadata.
Reproduction
With the filesystem huge-file feature, a 4,096-byte block and inode flag
0x00040000, encode an allocation count of one. The affected reader returns one sector instead of eight. Also grow an original regular file beyond 2 GiB on media lacking the large-file feature.Expected and actual behavior
Normalize allocation counts to sectors, encode matching units and publish required representation features within the same transaction. The affected helpers misinterpret counts and update size without the required superblock feature.
Environment and identity
Affected source: 2007c3bd, Integration graph 770e4e81. The original inode and superblock remain under their existing mount/transaction owner. This is a source and fixture finding; no boot-image reproduction is claimed. Last known working revision is unknown.
Evidence and prior checks
The inode format specifies allocation units and feature-dependent fields. Independent controls cover literal counts, flags, identity/checksums, format limits and journal interruption.
Tracking
Correction: #47.
erikinkinen referenced this issue from erix/docs2026-10-02 04:58:30 +02:00
erikinkinen referenced this issue2026-10-02 04:58:31 +02:00
erikinkinen referenced this issue from erix/integration2026-10-02 04:58:33 +02:00
The correction is ready in #47, including the independent format boundaries and interrupted original-journal controls. The issue remains open until the change is merged.