-
Notifications
You must be signed in to change notification settings - Fork 6k
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
(re-open) ZRAM info collector module (proc.plugin) #6424
Conversation
ZRAM: Implemented zram device id detection ZRAM: Implemented zram device enumeration WIP ZRAM: Memory usage graph (needs other graphs) ZRAM: Added ratio and efficiency graph ZRAM: Added chart description and context names, code formatting
{ | ||
snprintfz(filename, FILENAME_MAX, "/dev/%s", de->d_name); | ||
if (unlikely(stat(filename, &st) != 0)) | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey, it would be nice to not add one more code style
https://docs.netdata.cloud/contributing/#code-style
https://www.kernel.org/doc/html/v4.10/process/coding-style.html#placing-braces-and-spaces
@RaZeR-RBI I see the WIP label is still attached. Are you going to make changes to the PR? |
I've attached the WIP label in order to prevent merging due to reasons explained in the first post. If everything is ok (the bug is fixed) or if the label is misleading we can remove it 😉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I no longer get the crash I was getting before.
* ZRAM collector module ZRAM: Implemented zram device id detection ZRAM: Implemented zram device enumeration WIP ZRAM: Memory usage graph (needs other graphs) ZRAM: Added ratio and efficiency graph ZRAM: Added chart description and context names, code formatting * ZRAM: Proper handling of zram device removal * ZRAM: Added additional checks, removed redundant logging
Re-opening #6276 (initial PR with ZRAM module that was merged) in response to #6412 (double free and corruption).
I haven't reproduced the bug on my machines yet (my guess is that it may be tied to Linux distribution), but I've added a pair of additional checks that (possibly) could crash the app.
Any info about the environment where the bug was encountered is very appreciated. Sorry for inconvenience 😳