Add NULL checks to prevent segfaults when Kafka metadata contains NULL #428
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Application crashes with segmentation fault when calling
AdminClient.describeTopics()during Kafka broker restarts. The crash occurs when converting node metadata to JavaScript objects.Root Cause: During broker restarts, Kafka metadata can contain NULL node pointers or NULL host fields. The code dereferenced these NULL pointers without checks, causing segfaults.
Replication steps
Solution
Added defensive NULL checks in two functions:
ToV8Object()- Check if node pointer and host field are NULL before accessingFromDescribeTopicsResult()- Check leader, ISR, and replica nodes for NULL before conversionNULL values are now safely converted to JavaScript
nullinstead of crashing.Testing
Without Fix
With Fix
No segfault noticed