-
-
Notifications
You must be signed in to change notification settings - Fork 254
Fix null pointer dereference in pmproxy #2375
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
Conversation
|
I did quite extensive testing of this patch and so far, no crashes (core dumps) were observed with this patch applied. Unfortunately there is no direct way how to reliably reproduce this null pointer dereference, so it is not possible to test it with 100% certainty. |
A null pointer dereference in libpcp_web when handling battons causing pmproxy to crash (core dump). The crash happens from time to time when pmproxy is under load and serving data in paralel to more pmproxy clients. This patch fixes the null pointer dereference. Resolves: RHEL-70195
Resolves: bz2404769
Resolves: bz2404770
* No need to check for NULL before calling free() * Improved diagnostic messages
natoscott
left a comment
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.
@kurik I was reflecting further on this and I think we should not hide these conditions behind debug statements. Its OK to improve the resilience here but there are still bugs that need fixing. Could you drop the pmDebugOptions.series use, and change the fprintf statements to __pmNotify(LOG_ERR, ...) so that we get logs+timestamps when these things happen?
|
@natoscott Makes sense to me - reworked. |
A null pointer dereference in libpcp_web when handling battons causing pmproxy to crash (core dump). The crash happens from time to time when pmproxy is under load and serving data in paralel to more pmproxy clients. This patch fixes the null pointer dereference.
Resolves: RHEL-70195
Resolves: bz2401579