WIP: Apply conditional retained inode permissions #49

Draft
erikinkinen wants to merge 23 commits from feature/ext-retained-inode-permissions into feature/ext-encrypted-file-growth
Owner

Apply conditional retained inode permissions.

Depends on #48 (feature/ext-encrypted-file-growth).

  • Separate this feature from the preceding changes.
  • Link matching provider PRs and complete integrated acceptance.

Cross-repository API dependencies are still being mapped to their feature PRs.

Apply conditional retained inode permissions. Depends on #48 (`feature/ext-encrypted-file-growth`). - [x] Separate this feature from the preceding changes. - [ ] Link matching provider PRs and complete integrated acceptance. Cross-repository API dependencies are still being mapped to their feature PRs.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 12:22:01 +01:00
feat: Apply conditional retained inode permissions
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Failing after 5s
CI / test (push) Failing after 1m13s
b20bf7d9a8
Apply conditional retained inode permissions.
ci: Use shared development dependency profiles
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / test (push) Has been cancelled
CI / markdown (push) Has been cancelled
598f728f23
Keep authored manifests on main and select coordinated providers through Integration. Resolve branches once per run, retain the frozen snapshot and helper identity as artifacts, and use shared source checks instead of copied tests and guides.
ci: Declare policy helper and output boundaries
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Failing after 8s
CI / test (push) Failing after 2m38s
669376d85d
Select a disjoint operation parent for policy evidence and explicitly identify the helper checkout excluded from original component input. Keep the complete dependency policy and existing acceptance commands.
Repair the selected native permission feature without changing its preflight or authority rules. Use the actual invalid-argument result before effects and resolve the existing metadata helper within its original store/media family.
Keep the existing allocation-backed size helper and imports in their actual test-only callers. Remove the unused private re-export while retaining the production storage-backed mutation paths and every test implementation.
Keep the existing hosted controls on the actual admitted creation intent, move-only handle reservation and extent encoding interfaces. Preserve the same file access, block range, metadata assertions and negative controls; use the real installed handle row rather than indexing with a consumed reservation.
Remove the redundant parent-module extent import. The original block-map controls already import their defining module directly, so both native and hosted builds retain the same traversal implementation and tests without an unused alias.
fixup! feat: Apply conditional retained inode permissions
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Failing after 3s
CI / test (push) Failing after 1m30s
d69a169ba3
Explicitly admit writable media in the positive journal, undo and ACL-creation fixtures that own the actual writable block bytes. Preserve the production read-only empty mount and every explicit read-only refusal control instead of inheriting a nonexistent write grant from a read fixture.
Admit writable storage explicitly in the existing positive attribute-retirement, quota-transfer and undo-rollback fixtures. The actual byte effects, original journal barriers and every refusal assertion remain intact; production empty mounts and dedicated read-only controls keep their secure defaults.
Encode the existing 48-bit sector-overflow control under the format feature that actually admits its high count words. Preserve the independent maximum-count expectation and the no-allocation/no-write assertions instead of stopping at an unrelated missing-superblock-format refusal.
Complete positive fixture admission for real creation and dispatch transactions while preserving secure production defaults. Model the existing owned-buffer write-through barrier explicitly and keep foreign-route refusals. Select an ASCII fixture name before acquisition only for the legacy administrative-path metadata control; all original raw-byte native controls and metadata assertions remain unchanged.
Compare original inode checksums at the width physically stored by the selected inode format. Preserve full extended checksums and payload-corruption refusal. Declare the actual file-type feature in independently encoded acquisition media and select writable fixture authority only for positive operation/presence cases.
Select real writable fixture authority for streamed inheritance and model the existing owned in-memory write-through barrier. Inject failed publication at the actual parent directory sector and prove the selected refusal occurs. End restart fixtures volatile owners lexically without inventing cleanup behavior.
Align original acceptance controls with existing final-block ranges, encrypted growth, special hardlink metadata and held-destination lifetime contracts. Preserve exact dependency and malformed-framing errors with zero effects, denied device opening and crash-safe retention requirements. Bind data-before-commit observation to the original journal LBAs and real flush events, separating the committed home checkpoint.
Keep native ext mutation components byte-exact instead of applying legacy pathname UTF-8 policy. Share the existing native component framing and original physical name limit across held effects and journal replay, preserving separator, NUL, navigation and length refusals. Keep positive touch frames valid and check the actual special-alias link count while it exists.
Pass the unchanged original link-count oracle when the rename fixture checks special-file metadata through the shared observer.
Select this component retained-provider cohort explicitly for work-branch CI, preserving automatic current-main provider policy after integration. Keep dependency declarations on main, retain the actual frozen-source verification gate, and avoid copying shared tests or helper implementation into the component.
Keep constant-time in the complete provider set while selecting its canonical main through the maintained resolver. Companion rows describe feature overrides only; preserve all other reviewed provider branches.
Retire supported special-inode hardlinks through the existing administrative unlink operation without granting device I/O or widening other exact roles. Keep explicit known-kind admission and verify alias and final-link reclamation, unchanged neighboring special inodes and complete ext2/ext3/ext4 filesystem consistency.
Document physical inode checksum width and component-owned provider selection. Reflow existing documentation and express the two long authority/durability tables as labelled lists without changing their requirements or repository template sections.
Exercise the same original special inode through the unchanged legacy read, rename and touch refusals. Check final reclamation clears inode storage and leaves no orphan while neighboring special objects and external filesystem consistency remain intact.
fixup! feat: Apply conditional retained inode permissions
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Failing after 2m38s
56aebff45b
Observe reclaimed inode bytes at their previously admitted original extent instead of treating a freed inode as a live checksummed object. Keep explicit zero storage, orphan and external consistency assertions.
fixup! feat: Apply conditional retained inode permissions
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Successful in 2m53s
dc808bfada
Reserve distinct test-owned checker image names for concurrent orphan restart and final-close controls, including repeated use of the same filesystem label. Preserve actual e2fsck execution and successful removal of each original output.
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Successful in 2m53s
This pull request has changes conflicting with the target branch.
  • .github/workflows/ci.yml
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'feature/ext-retained-inode-permissions:feature/ext-retained-inode-permissions'
git switch 'feature/ext-retained-inode-permissions'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'feature/ext-encrypted-file-growth'
git merge --no-ff 'feature/ext-retained-inode-permissions'
git switch 'feature/ext-retained-inode-permissions'
git rebase 'feature/ext-encrypted-file-growth'
git switch 'feature/ext-encrypted-file-growth'
git merge --ff-only 'feature/ext-retained-inode-permissions'
git switch 'feature/ext-retained-inode-permissions'
git rebase 'feature/ext-encrypted-file-growth'
git switch 'feature/ext-encrypted-file-growth'
git merge --no-ff 'feature/ext-retained-inode-permissions'
git switch 'feature/ext-encrypted-file-growth'
git merge --squash 'feature/ext-retained-inode-permissions'
git switch 'feature/ext-encrypted-file-growth'
git merge --ff-only 'feature/ext-retained-inode-permissions'
git switch 'feature/ext-encrypted-file-growth'
git merge 'feature/ext-retained-inode-permissions'
git push origin 'feature/ext-encrypted-file-growth'
Sign in to join this conversation.
No description provided.