20251007-linuxkm-fortify-source-sunrise#9280
Merged
kaleb-himes merged 1 commit intowolfSSL:masterfrom Oct 7, 2025
Merged
Conversation
…on kernels <5.18 (shim conflicts), and add WC_FORCE_LINUXKM_FORTIFY_SOURCE for future use.
Contributor
Author
|
retest this please |
dgarske
approved these changes
Oct 7, 2025
kaleb-himes
approved these changes
Oct 7, 2025
Contributor
kaleb-himes
left a comment
There was a problem hiding this comment.
Thanks @douzzer (tested on RHEL 8.10 with kernel 4.18)
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.
linuxkm/linuxkm_wc_port.h: disableCONFIG_FORTIFY_SOURCEmodule-wide on kernels <5.18 (shim conflicts), and addWC_FORCE_LINUXKM_FORTIFY_SOURCEfor future use.tested with
CONFIG_FORTIFY_SOURCEforced on for kernels 5.16, 5.17, 5.18, and 5.19. 6.1 and 6.12 fortifying kernels are already tested IRL in the nightlies.