[BUG] Packaged realm fixtures omit full-width device inodes #110

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

Summary

The packaged realm-binding fixture omits both wide device inodes. Its generator passes full-width device numbers to debugfs mknod, which rejects those arguments but still exits 0. Image preparation can therefore appear successful with missing metadata fixtures.

Reproduction

At Integration 5cdd151b807b2e3bfc914d58c40fb7da413eb49c, run:

python3 -B -Werror tests/realm_link_fixtures_test.py

Expected and actual behavior

The character inode must retain device 2748:913170 and the block inode 4095:1048575. With debugfs 1.47.3, both creation commands print Usage; subsequent lookup reports missing files. Ordinary device tuples, FIFO and symlinks are created correctly. The host control fails on missing character-special metadata.

Environment and identity

Linux host, disposable 24 MiB ext4 image, e2fsprogs debugfs 1.47.3. These inodes are fixture metadata and confer no native device authority.

Evidence and prior checks

The actual generator is used by packaging and the host control. Independently tested repair commands create the typed inode with device 0:0, then set the literal extended encoding in its original inode words. Real debugfs decoding confirms both full-width tuples and mode 0000.

Tracking

Repair the shared generator and keep type, mode, full-width device identity, alias and native-route-denial checks. Name each test row so a failed lookup identifies the affected fixture.

## Summary The packaged realm-binding fixture omits both wide device inodes. Its generator passes full-width device numbers to `debugfs mknod`, which rejects those arguments but still exits 0. Image preparation can therefore appear successful with missing metadata fixtures. ## Reproduction At Integration `5cdd151b807b2e3bfc914d58c40fb7da413eb49c`, run: ```sh python3 -B -Werror tests/realm_link_fixtures_test.py ``` ## Expected and actual behavior The character inode must retain device 2748:913170 and the block inode 4095:1048575. With debugfs 1.47.3, both creation commands print Usage; subsequent lookup reports missing files. Ordinary device tuples, FIFO and symlinks are created correctly. The host control fails on missing character-special metadata. ## Environment and identity Linux host, disposable 24 MiB ext4 image, e2fsprogs debugfs 1.47.3. These inodes are fixture metadata and confer no native device authority. ## Evidence and prior checks The actual generator is used by packaging and the host control. Independently tested repair commands create the typed inode with device 0:0, then set the literal extended encoding in its original inode words. Real debugfs decoding confirms both full-width tuples and mode 0000. ## Tracking Repair the shared generator and keep type, mode, full-width device identity, alias and native-route-denial checks. Name each test row so a failed lookup identifies the affected fixture.
Author
Owner

The generator fix creates both typed device inodes with supported zero tuples, then sets their full-width extended encodings. Real debugfs reads confirm 2748:913170 and 4095:1048575 with mode 0000. The ordinary device, FIFO, alias and symlink cases remain intact; inode metadata grants no native device route.

The [generator fix](https://git.erikinkinen.fi/erix/integration/commit/c72c248f0d7fb21a6ca6ce8a3dcf964530536f81) creates both typed device inodes with supported zero tuples, then sets their full-width extended encodings. Real debugfs reads confirm 2748:913170 and 4095:1048575 with mode 0000. The ordinary device, FIFO, alias and symlink cases remain intact; inode metadata grants no native device route.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:16 +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#110
No description provided.