mnt_newapi: use FSCONFIG_SET_STRING for key=value mount options - #254
Merged
robertswiecki merged 1 commit intoMar 4, 2026
Merged
Conversation
createFilesystemMount() passed all mount options via FSCONFIG_SET_FLAG, which fails for key=value parameters (e.g. size=67108864). Detect '=' in each option and dispatch to FSCONFIG_SET_STRING with separate key and value arguments.
koki-develop
marked this pull request as ready for review
March 3, 2026 08:44
Collaborator
|
Good catch! Thank you |
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
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.
createFilesystemMount()usesFSCONFIG_SET_FLAGfor key=value mount options #253Summary
Fixed
createFilesystemMount()to useFSCONFIG_SET_STRINGfor key=value format options, instead of passing all mount options viaFSCONFIG_SET_FLAG.Fixes an issue where mounts with key=value options such as
size=67108864would fail withEINVALin environments where the new mount API is active (kernel >= 6.3).Background
createFilesystemMount()was splitting theoptionsstring by commas and passing all tokens viaFSCONFIG_SET_FLAG. This works for boolean flags (ro,noexec), but fails for key=value parameters (size=67108864) because the kernel requiresFSCONFIG_SET_STRING, which accepts the key and value as separate arguments.Referenced the existing usage of
FSCONFIG_SET_STRINGincreateDetachedTmpfs()in the same file:Changes
Checks whether each option contains
=and dispatches to the appropriatefsconfigcommand:=→FSCONFIG_SET_STRING(splits and passes key and value separately)=→FSCONFIG_SET_FLAG(existing behavior)Test output
Full log output