[BUG] OPEN hides publication uncertainty as invalid arguments #23

Closed
opened 2026-10-12 16:33:06 +02:00 by erikinkinen · 1 comment
Owner

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:

cargo test --all-targets --all-features conditional_plain_uncertainty_disables_endpoint_even_after_reset

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 affected open_with_keys maps every mount lookup failure to IPC_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.

## 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: ```sh cargo test --all-targets --all-features conditional_plain_uncertainty_disables_endpoint_even_after_reset ``` 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 affected `open_with_keys` maps every mount lookup failure to `IPC_RESULT_INVALID_ARGUMENT` (`2`), hiding the poisoned state. ## Environment and identity Affected: [E2fsd 55a6d1e4](https://git.erikinkinen.fi/erix/e2fsd/commit/55a6d1e470bf1ea29745dcf3ffa1a7c6094ff2d2). The host fixture supplies its own writable ext medium and existing mount. ## Evidence and prior checks [The fix](https://git.erikinkinen.fi/erix/e2fsd/commit/6aafde2b9a7f66a1a02e6019e92b9b0ded742bfa) 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](https://git.erikinkinen.fi/erix/e2fsd/actions/runs/400). ## Tracking Related: [journal durability](https://git.erikinkinen.fi/erix/e2fsd/issues/17), [E2fsd PR 3](https://git.erikinkinen.fi/erix/e2fsd/pulls/3), [Phase 6](https://git.erikinkinen.fi/erix/integration/issues/65).
Author
Owner

OPEN now preserves terminal publication uncertainty and maps only a missing mount to invalid arguments. Fixed in this commit.

OPEN now preserves terminal publication uncertainty and maps only a missing mount to invalid arguments. Fixed in [this commit](https://git.erikinkinen.fi/erix/e2fsd/commit/6aafde2b9a7f66a1a02e6019e92b9b0ded742bfa).
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#23
No description provided.