[BUG] EXT link and rename verifiers expect obsolete inode results #131

Closed
opened 2026-10-15 16:41:55 +02:00 by erikinkinen · 2 comments
Owner

Summary

The EXT link and rename verifiers reject current special-inode results. They expect kind NONE, while E2fsd reports explicit FIFO, character and block types. The link verifier also expects a character-inode hard link to be denied, although the provider supports that namespace operation.

Reproduction

At Integration 104fdec3, run:

./scripts/run-scenario.sh tests/scenarios/subsystem-e2fs-fat-ext2-links-positive.toml components.toml

The same mismatch affects the ext2/3/4 link and rename scenarios. A character stat with kind 5 cannot satisfy the verifier's kind-0 check; its positive mock supplies the obsolete value.

Expected and actual behavior

Accept the exact inode type matching its mode and verify hard-link identity and cleanup. Incorrect types, unexpected link counts, provider errors and successful device opens must still fail.

All six original guests exit with status 41 instead of 33. Link cases reach LARGE_EXT_CREATED_DONE; rename cases also reach EXT_LINKS_DONE before SERVICE_FAIL. This locates the verifier stage but does not identify the exact failed operation.

Environment and identity

Integration 104fdec3, orchestration supplier 7769fb52, Rootd b2933983, E2fsd a0247825, Vfsd 40d3e38b, IPC 647f5394. The release scenarios use ext2/3/4 fixture media and the existing VFS route. Descriptive inode types and namespace aliases grant no device endpoint. Last known working revision is unknown.

Evidence and prior checks

Original VM run. The link verifier and provider fixtures expose the differing contracts.

Tracking

  • Correct both verifiers' descriptive inode-kind checks.
  • Verify special-inode alias creation and cleanup while retaining device-open refusal.
  • Replace stale positive fixtures and cover incorrect provider results.
  • Publish the supplier and select its immutable revision in Rootd.
  • Pass the unchanged six guest scenarios on the repaired graph.
## Summary The EXT link and rename verifiers reject current special-inode results. They expect kind `NONE`, while E2fsd reports explicit FIFO, character and block types. The link verifier also expects a character-inode hard link to be denied, although the provider supports that namespace operation. ## Reproduction At Integration `104fdec3`, run: ```sh ./scripts/run-scenario.sh tests/scenarios/subsystem-e2fs-fat-ext2-links-positive.toml components.toml ``` The same mismatch affects the ext2/3/4 link and rename scenarios. A character stat with kind `5` cannot satisfy the verifier's kind-`0` check; its positive mock supplies the obsolete value. ## Expected and actual behavior Accept the exact inode type matching its mode and verify hard-link identity and cleanup. Incorrect types, unexpected link counts, provider errors and successful device opens must still fail. All six original guests exit with status `41` instead of `33`. Link cases reach `LARGE_EXT_CREATED_DONE`; rename cases also reach `EXT_LINKS_DONE` before `SERVICE_FAIL`. This locates the verifier stage but does not identify the exact failed operation. ## Environment and identity Integration `104fdec3`, orchestration supplier `7769fb52`, Rootd `b2933983`, E2fsd `a0247825`, Vfsd `40d3e38b`, IPC `647f5394`. The release scenarios use ext2/3/4 fixture media and the existing VFS route. Descriptive inode types and namespace aliases grant no device endpoint. Last known working revision is unknown. ## Evidence and prior checks [Original VM run](https://git.erikinkinen.fi/erix/integration/actions/runs/2684). The [link verifier](https://git.erikinkinen.fi/erix/integration/src/commit/7769fb520cd95da1d32d28077033f5c8fa8cc7b7/lib/rootd-integration-orchestration/src/verification/vfs_ext_links.rs) and [provider fixtures](https://git.erikinkinen.fi/erix/e2fsd/src/commit/a0247825be6e950784b1cd1aac26afb0ab86ba66/src/media/fixture_link_tests.rs) expose the differing contracts. ## Tracking - [x] Correct both verifiers' descriptive inode-kind checks. - [x] Verify special-inode alias creation and cleanup while retaining device-open refusal. - [x] Replace stale positive fixtures and cover incorrect provider results. - [x] Publish the supplier and select its immutable revision in Rootd. - [x] Pass the unchanged six guest scenarios on the repaired graph.
Author
Owner

Published the verifier repair in 837b00cd. It checks the provider’s actual special-inode kinds and descriptive character hardlinks, including correlated metadata, link counts, denied device opens and temporary-name cleanup. Rootd’s dependency adoption is underway; the six unchanged guest cases remain pending.

Published the verifier repair in [837b00cd](https://git.erikinkinen.fi/erix/integration/commit/837b00cdffec23379484f34364d97ca35874aa04). It checks the provider’s actual special-inode kinds and descriptive character hardlinks, including correlated metadata, link counts, denied device opens and temporary-name cleanup. Rootd’s dependency adoption is underway; the six unchanged guest cases remain pending.
Author
Owner

All six unchanged EXT2/3/4 link and rename scenarios now pass with complete guest captures and confirmed host-process cleanup. The repaired verifier supplier is 837b00cd, selected by Rootd ff0bd1ef through Integration f467304f. All five acceptance criteria are complete; closing this verifier regression.

All six unchanged EXT2/3/4 link and rename scenarios now pass with complete guest captures and confirmed host-process cleanup. The repaired verifier supplier is [837b00cd](https://git.erikinkinen.fi/erix/integration/commit/837b00cdffec23379484f34364d97ca35874aa04), selected by [Rootd ff0bd1ef](https://git.erikinkinen.fi/erix/rootd/commit/ff0bd1ef6a6aad09e3f0bf39c7443ece4d1847dc) through [Integration f467304f](https://git.erikinkinen.fi/erix/integration/commit/f467304fc8f99f4b7d6cd7e23a1254d08e510cef). All five acceptance criteria are complete; closing this verifier regression.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:17 +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/integration#131
No description provided.