[BUG] OPEN hides publication uncertainty as invalid arguments #23
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#23
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
OPEN reports invalid arguments after E2fsd has stopped accepting operations because a filesystem write could not be confirmed. The caller loses the terminal publication error.
Reproduction
From E2fsd, run:
The fixture injects an uncertain write during a retained-entry mutation, then opens the mounted root directory before and after provider reset. It records device writes to detect any further effects.
Expected and actual behavior
Both OPEN attempts must preserve the provider's terminal publication error (
4294967295) without new writes. The affectedopen_with_keysmaps every mount lookup failure toIPC_RESULT_INVALID_ARGUMENT(2), hiding the poisoned state.Environment and identity
Affected: E2fsd 55a6d1e4. The host fixture supplies its own writable ext medium and existing mount.
Evidence and prior checks
The fix maps only a missing mount to invalid arguments and preserves other failures. The regression checks both OPEN attempts and unchanged write counts in CI run 400.
Tracking
Related: journal durability, E2fsd PR 3, Phase 6.
OPEN now preserves terminal publication uncertainty and maps only a missing mount to invalid arguments. Fixed in this commit.