[BUG] Valid short EXT inodes are rejected by a full-width checksum comparison #22
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#22
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
The inode verifier rejects valid short inodes by comparing their stored 16-bit checksum with a full 32-bit accumulator.
Reproduction
At the original source, encode a 128-byte inode with
metadata_csum, seed0x12345678, inode 2, generation 1 and mode040755; leave other fields zero. The accumulator is0x66c76e06. Store its low word0x6e06at bytes 124–125.Expected and actual behavior
Compare the checksum at its represented width. The high word is present only within initialized extra inode fields; preserve full-width checking when it exists and include other extra bytes as ordinary covered data.
Environment and identity
Evidence and prior checks
The primary inode format defines checksum fields and initialized extra size. Independent CRC, corruption, wrong-identity and unchanged-refusal-buffer controls are required.
Tracking
Fixes and independent checksum coverage are included in #44.