-
Notifications
You must be signed in to change notification settings - Fork 169
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
NULL pointer dereference in kmod driver while hot plugging a CPU #2251
Comments
I believe this is a regression, this used to work with an older version of the kernel driver (draios/sysdig#744) and it's actually shockingly easier to reproduce:
This behavior also contradicts what's written here: https://github.com/falcosecurity/libs/blob/7.3.0%2Bdriver/driver/main.c#L475-L482
|
Hi! Thanks for the detailed bug report! |
Question, did you by chance upgrade your running kernel in the meantime? |
Moving to libs. |
/milestone next-driver |
Proposed a fix in #2252. |
I never actually used that ancient version in production. Actually this is my very first time using falco, i just got curious and started looking for a possible explanation to this bug, i found that old commit mentioning hot plugging and verified that it was working correctly on a throwaway node. |
Describe the bug
The kmod driver doesn't handle CPU hot plugging gracefully. Maybe it's not a common use case (that is, it doesn't really happen that often during a workload) but it did happen to me.
How to reproduce it
Happened once randomly while hot plugging a core, can be easily reproduced running the following commands in a loop
Expected behaviour
Falco's kmod driver should handle CPU hot plugging gracefully.
Screenshots
No screenshot, but i'll do you one better, kernel oops (this is from my debug kernel, but it does happen on 5.15.0-67-generic as well):
kgdb
Environment
Additional context
The text was updated successfully, but these errors were encountered: