[BUG] Journal operations lack durable ordering and split atomic commits #17
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#17
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 JBD2 writer commits descriptor-sized chunks separately and omits durability barriers around journal publication, checkpointing and recovery. A storage interruption can therefore expose part of one filesystem operation.
Reproduction
At the original source, inspect
write_internal_journal_transactionsandwrite_internal_journal_transaction_chunk. An operation larger than one descriptor receives several transaction identities and commits. The surrounding writer and recovery paths do not flush their held device routes.Expected and actual behavior
Keep one transaction identity and one commit for the complete operation. Persist descriptors and data before the commit, persist home blocks before retiring the journal, and preserve the original filesystem/internal-or-external-journal selection. Refuse unsupported durability before effects and retain fail-stop custody after uncertainty.
The original source splits commits and has no barriers. Read-after-write checks cannot establish persistence.
Environment and identity
Evidence and prior checks
The JBD2 specification defines transaction publication. Independent volatile/stable media controls must cover chained descriptors, original routes, lost completions, partial checkpoints, checksum dialects, revocation and full/fast-recovery storage reuse.
Tracking
The fix is implemented in #45. Compatibility persistence and release-image acceptance remain tracked in Posixd #28.
erikinkinen referenced this issue2026-10-02 03:28:17 +02:00
erikinkinen referenced this issue from erix/posixd2026-10-02 03:28:18 +02:00
erikinkinen referenced this issue from erix/docs2026-10-02 03:28:19 +02:00
erikinkinen referenced this issue from erix/integration2026-10-02 03:28:20 +02:00
The fix is ready for review in #45 at
ec9d6a85. Multi-descriptor writes now have one commit, and the original filesystem/journal barriers surround publication, checkpoint and recovery retirement. Independent controls also prevent a callback from hiding a failed staged member and committing an earlier prefix. Current CI passes the 515-test component suite. Hardware power-loss and release-image acceptance remain separate.