20251017-linuxkm-signal-handling-tweaks#9318
Merged
philljj merged 6 commits intowolfSSL:masterfrom Oct 18, 2025
Merged
Conversation
…hooks.c, linuxkm/lkcapi_glue.c: * add WC_SIG_IGNORE_BEGIN(), WC_SIG_IGNORE_END(), wc_linuxkm_sig_ignore_begin(), wc_linuxkm_sig_ignore_end(); * move WC_CHECK_FOR_INTR_SIGNALS() and WC_RELAX_LONG_LOOP() definitions outside the BUILDING_WOLFSSL gate; * refactor linuxkm_lkcapi_registering_now as a wolfSSL_Atomic_Int and use it as a mutex for linuxkm_lkcapi_register() and linuxkm_lkcapi_unregister(); * add WC_SIG_IGNORE_BEGIN()...WC_SIG_IGNORE_END() wrappers around all relevant critical spans in linuxkm glue.
…g, pending resolution of "dwarf_get_units failed" on Azure kernel 6.14 image.
…r verifyCore and my_kallsyms_lookup_name, and use the latter to reach verifyCore on old FIPS. also tweak the In-core integrity hash check failure." message to supply module-update-fips-hash instructions.
Contributor
|
🛟 Devin Lifeguard found 2 likely issues in this PR
@douzzer |
…C_SIG_IGNORE_BEGIN().
…LD to, reproducible-build AM_CFLAGS, and always add -gdwarf-4 to AM_CFLAGS when ENABLED_LINUXKM; .github/workflows/linuxkm.yml: restore as-was, but change from oldconfig to olddefconfig.
Contributor
Author
|
retest this please |
…ng kernel headers (needed for kernel <=4.9).
Contributor
Author
|
retest this please |
philljj
approved these changes
Oct 18, 2025
Contributor
philljj
left a comment
There was a problem hiding this comment.
Thanks for fixing the dwarf issue!
Contributor
Author
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,wolfssl/wolfcrypt/types.h,linuxkm/module_hooks.c,linuxkm/lkcapi_glue.c:WC_SIG_IGNORE_BEGIN(),WC_SIG_IGNORE_END(),wc_linuxkm_sig_ignore_begin(),wc_linuxkm_sig_ignore_end();WC_CHECK_FOR_INTR_SIGNALS()andWC_RELAX_LONG_LOOP()definitions outside theBUILDING_WOLFSSLgate;verifyCoreandmy_kallsyms_lookup_name, and use the latter to reachverifyCoreon old FIPS;module-update-fips-hashinstructions;linuxkm_lkcapi_registering_nowas awolfSSL_Atomic_Intand use it as a mutex forlinuxkm_lkcapi_register()andlinuxkm_lkcapi_unregister();WC_SIG_IGNORE_BEGIN()...WC_SIG_IGNORE_END()wrappers around all relevant critical spans in linuxkm glue..github/workflows/linuxkm.yml: comment out--enable-linuxkm-pieconfig, pending resolution of "dwarf_get_units failed" on Azure kernel 6.14 image.tested with
wolfssl-multi-test.sh ... '.*insmod.*'with multi-test fixed to recognize the new kernel hash check failure message.