20260122-toolchain-workarounds #9704
Merged
+15
−5
Conversation
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
…INUXKM_PIE setup, i.e. always usable.
…levels are disabled, in WOLFSSL_WC_DILITHIUM setup.
dgarske
approved these changes
Jan 23, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
linuxkm/Kbuild: moveFORCE_GLOBAL_OBJTOOL_OFFsetup outsideENABLED_LINUXKM_PIEsetup, i.e. always usable.wolfssl/wolfcrypt/dilithium.h: add a check for whether all supported levels are disabled, inWOLFSSL_WC_DILITHIUMsetup.Note, the Kbuild tweak is to work around targets (in this case Kubuntu) with kernel configs that run
objtoolon the fully linked module, ignoringOBJECT_FILES_NON_STANDARD := yannotations, then elevate the warnings to fatal errors.The dilithium.h tweak is to work around a toolchain defect wherein
unit.testtargeting armeb (big endian ARM32) with sanitizers, running underqemu-armeb, produces false positive out-of-bounds memory access reports due to internal sanitizer tooling corruption (UB). That test is probably not sustainable, but for now this tweak stabilizes it.