Skip to content

Conversation

@kurik
Copy link
Contributor

@kurik kurik commented Oct 17, 2025

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

@kurik
Copy link
Contributor Author

kurik commented Oct 17, 2025

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.

kurik added 4 commits October 22, 2025 11:33
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
* No need to check for NULL before calling free()
* Improved diagnostic messages
Copy link
Member

@natoscott natoscott left a 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?

@kurik
Copy link
Contributor Author

kurik commented Oct 23, 2025

@natoscott Makes sense to me - reworked.

@natoscott natoscott merged commit 6e99532 into performancecopilot:main Oct 24, 2025
22 checks passed
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

Successfully merging this pull request may close these issues.

2 participants