feat: Support per-mount id_mapping#227
Open
Zephyrcf wants to merge 3 commits into
Open
Conversation
Zephyrcf
requested review from
bergwolf,
eryugey,
imeoer and
liubogithub
as code owners
July 3, 2026 09:32
This was referenced Jul 5, 2026
BraveY
approved these changes
Jul 21, 2026
BraveY
left a comment
BraveY
left a comment
There was a problem hiding this comment.
LGTM. Thanks a lot for the helpful PR.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR implements per-mount ID mapping for the VFS layer, fixes a remapping arithmetic underflow bug, and extends ID remapping support to the async server/VFS path. Previously, UID/GID remapping was a single global VFS option; now each mounted filesystem can have its own independent mapping, enabling mixed-identity container/VM scenarios where different mounts need different user namespace translations.