[BUG] Read-only permission evidence becomes INTERNAL #32

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

Summary

Vfsd reports an internal error when a read-only mount refuses write permission. This hides the expected policy refusal from the caller.

Reproduction

From Vfsd, run:

cargo test --all-targets --all-features readonly_mount_preserves_read_acquisition_and_original_cleanup
cargo test --all-targets --all-features crossed_readonly_mount_denies_write_evidence_under_a_writable_scope

The fixtures prepare a writable acquisition scope over a read-only mount and request write permission for the root, current directory, or an acquired file. The second fixture crosses into a read-only child mount.

Expected and actual behavior

The permission response must contain VFS_ACQUISITION_EVIDENCE_READ_ONLY_V1 (0x100) and no snapshot. The affected dispatcher passes this valid result through the generic result filter and returns IPC_RESULT_INTERNAL (5). The mount check itself correctly refuses the request before provider I/O.

Environment and identity

Affected: Vfsd 8c42847b. The host fixtures use explicitly configured mount policy and acquired handles.

Evidence and prior checks

The fix preserves 0x100 only in the permission-evidence response family. Generic transport result validation remains unchanged. Both regression controls pass in CI run 356.

Tracking

Related: mount-policy enforcement, Vfsd PR 3, Phase 6.

## Summary Vfsd reports an internal error when a read-only mount refuses write permission. This hides the expected policy refusal from the caller. ## Reproduction From Vfsd, run: ```sh cargo test --all-targets --all-features readonly_mount_preserves_read_acquisition_and_original_cleanup cargo test --all-targets --all-features crossed_readonly_mount_denies_write_evidence_under_a_writable_scope ``` The fixtures prepare a writable acquisition scope over a read-only mount and request write permission for the root, current directory, or an acquired file. The second fixture crosses into a read-only child mount. ## Expected and actual behavior The permission response must contain `VFS_ACQUISITION_EVIDENCE_READ_ONLY_V1` (`0x100`) and no snapshot. The affected dispatcher passes this valid result through the generic result filter and returns `IPC_RESULT_INTERNAL` (`5`). The mount check itself correctly refuses the request before provider I/O. ## Environment and identity Affected: [Vfsd 8c42847b](https://git.erikinkinen.fi/erix/vfsd/commit/8c42847b175abd4260f69ffc67cbf23d41aa94a7). The host fixtures use explicitly configured mount policy and acquired handles. ## Evidence and prior checks [The fix](https://git.erikinkinen.fi/erix/vfsd/commit/15aecb9b427467774df26f13f37c367e471b04c0) preserves `0x100` only in the permission-evidence response family. Generic transport result validation remains unchanged. Both regression controls pass in [CI run 356](https://git.erikinkinen.fi/erix/vfsd/actions/runs/356). ## Tracking Related: [mount-policy enforcement](https://git.erikinkinen.fi/erix/vfsd/issues/11), [Vfsd PR 3](https://git.erikinkinen.fi/erix/vfsd/pulls/3), [Phase 6](https://git.erikinkinen.fi/erix/integration/issues/65).
Author
Owner

The permission response now preserves the read-only evidence code in its own response family. Fixed in this commit.

The permission response now preserves the read-only evidence code in its own response family. Fixed in [this commit](https://git.erikinkinen.fi/erix/vfsd/commit/15aecb9b427467774df26f13f37c367e471b04c0).
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:20 +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/vfsd#32
No description provided.