Skip to content
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

Work around Linux 5.8's unexporting of native_write_cr4 #1

Closed
solardiz opened this issue Aug 11, 2020 · 2 comments
Closed

Work around Linux 5.8's unexporting of native_write_cr4 #1

solardiz opened this issue Aug 11, 2020 · 2 comments
Assignees

Comments

@solardiz
Copy link
Contributor

Linux 5.8 no longer exports the native_write_cr4 symbol unless CONFIG_LKDTM is enabled. We use that symbol, and need to work around that, perhaps by using kallsyms_lookup_name to locate it.

Reference: https://www.openwall.com/lists/lkrg-users/2020/08/07/1

@solardiz
Copy link
Contributor Author

We believe this is fixed with 671b079, although more testing is needed. Closing the issue for now (can reopen if necessary).

@morfikov
Copy link
Contributor

I can confirm that it builds, at least on:

# cat /proc/version
Linux version 5.8.1-amd64 (morfik@morfikownia) (gcc (Debian 10.2.0-5) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP PREEMPT Thu Aug 13 13:14:40 CEST 2020

itoffshore referenced this issue Nov 12, 2021
Starting from the commit 066f883
LKRG can't be compiled without CONFIG_SECCOMP. Let's fix it here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants