-
Notifications
You must be signed in to change notification settings - Fork 52
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
Potential NULL pointer dereference bug in callInternal() #247
Comments
Thanks for finding this issue. Would you like to submit a PR to fix it? |
Hi I was wondering if this issue is still open and if so I would like to work on this :) |
Yes. It's still open now and welcome the contributions! |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Hi, I would like to try and fix this. Assigning myself |
I have made some changes in the code. Could anyone please verify if it is correct and suggest me if any modifications are needed?
|
I think this change is fine. Please follow https://github.com/kubernetes-client/c/blob/master/code-check/code-style-check.md to check the code style and then submit a PR for formal review. Thank you. |
Working on some other issue, so unassigning myself. |
In the function callInternal(), client->client->dataReceived is dereferenced unconditionally before it is checked for NULL:
https://github.com/kubernetes-client/c/blob/master/kubernetes/src/generic.c#L62
The text was updated successfully, but these errors were encountered: