Avoid passing __GFP_HIGHMEM on newer kernels#1746
Merged
robertbaldyga merged 1 commit intoOpen-CAS:masterfrom Apr 7, 2026
Merged
Avoid passing __GFP_HIGHMEM on newer kernels#1746robertbaldyga merged 1 commit intoOpen-CAS:masterfrom
robertbaldyga merged 1 commit intoOpen-CAS:masterfrom
Conversation
Since 5.18 vmalloc automatically allocates from highmem when possible, therefore this flag is not necessary and on newer kernels there is a warning generated if caller passes __GFP_HIGHMEM. Since kernels older than 5.18 still need it, simply mask it out in the configure wrapper for pgprot-less variant. Signed-off-by: Robert Baldyga <robert.baldyga@unvertical.com>
robertbaldyga
force-pushed
the
vmalloc-highmem-fix
branch
from
6b3eb57 to
1cc7dbe
Compare
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
1 participant
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.
Since 5.18 vmalloc automatically allocates from highmem when possible, therefore this flag is not necessary and on newer kernels there is a warning generated if caller passes __GFP_HIGHMEM.
Since kernels older than 5.18 still need it, simply mask it out in the configure wrapper for pgprot-less variant.