-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LKRG: FATAL: Can't find 'tracepoints_mutex' #334
Comments
@Evolto2019 Thank you for reporting this. My best guess is you don't have @Adam-pi3 Would it be safe to skip locking this mutex when it doesn't exist? If so, do you prefer we check at runtime (make failure of this symbol lookup non-fatal, maybe an |
@solardiz Thanks for the reply. I've done a quick look at my kconfig and didn't find |
@Evolto2019 Thank you. This should be an easy fix for us, but I'll wait for Adam's comments on how to fix it. |
@solardiz yes, it looks correct. Sounds like |
@Adam-pi3 My understanding is that compiler optimizations could mangle the name (and much more) of a static function, but |
@Evolto2019 We think this issue is fixed - can you please test and confirm? Thank you! |
LKRG fails to start after commit ee41d81 and gives error message:
LKRG: ALIVE: Loading LKRG
LKRG: ISSUE: Can't enforce SELinux validation (CONFIG_GCC_PLUGIN_RANDSTRUCT detected)
LKRG: ISSUE: [kretprobe] register_kretprobe() for <ovl_dentry_is_whiteout> failed! [err=-2]
LKRG: ISSUE: Can't hook 'ovl_dentry_is_whiteout'. This is expected when OverlayFS is not used.
LKRG: FATAL: Can't find 'tracepoints_mutex'
LKRG: FATAL: Can't create database
LKRG: DYING: Not loading LKRG (initialization failed)
p_exploit_detection_exit+0x2e/0xa0 [lkrg]
init_module+0x408/0x2000 [lkrg]
p_offload_cache_delete+0x11/0x40 [lkrg]
init_module+0x418/0x2000 [lkrg]
printk: legacy console [lkrg0] disabled
I have no idea what "tracepoints_mutex" is, can it be relevant to some hardened kconfig options? I'm currently on Linux hardened 6.8.6.
The text was updated successfully, but these errors were encountered: