[BUG] OPEN hides publication uncertainty as invalid arguments #16
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/fatd#16
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 Fatd has stopped accepting operations because a filesystem write could not be confirmed. The caller loses the terminal publication error.
Reproduction
From Fatd, run:
The fixture loses a completion after a target write, then opens the mounted root directory. It also resets the provider and checks that ordinary operations remain disabled without further device calls.
Expected and actual behavior
OPEN must preserve
IPC_RESULT_PUBLICATION_UNCERTAIN(4294967295). The affected code maps everyfind_mountfailure toIPC_RESULT_INVALID_ARGUMENT(2), including the error from a poisoned provider. The reproduced assertion receivesErr(2)instead ofErr(4294967295).Environment and identity
Affected: Fatd 21102ceb. The host test injects a lost write completion on its own FAT12 medium.
Evidence and prior checks
The fix maps only a missing mount to invalid arguments and preserves other failures. The regression passes in CI run 288.
Tracking
Related: Fatd PR 3, Phase 6.
OPEN now preserves terminal publication uncertainty and maps only a missing mount to invalid arguments. Fixed in this commit.