gnmi_server: fix nil-resp panic when CRL fetch fails#658
Open
SAY-5 wants to merge 1 commit into
Open
Conversation
http.Get() returns (nil, err) on network-level failures (DNS, connection refused, TLS handshake, timeout before any response). TryDownload() saved the defer inside `if resp != nil` but then unconditionally dereferenced `resp.StatusCode` in the next line, so any non-transport failure panicked the gNMI server with a nil pointer dereference. Return early on err != nil, then defer close and check StatusCode. Behavior otherwise unchanged. Closes sonic-net#630. Signed-off-by: SAY-5 <say.apm35@gmail.com>
|
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sneelam20
approved these changes
Apr 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #630.
Problem
TryDownloadingnmi_server/clientCertAuth.gounconditionally dereferencesresp.StatusCodeafterhttp.Get(url), buthttp.Getreturns(nil, err)on network-level failures (DNS resolution, connection refused, TLS handshake failure, timeout before response, etc.). Any of these paths panics the gNMI server withnil pointer dereference.Fix
Short-circuit on
err != nilbefore touchingresp, matching the standard Go pattern. Log the HTTP status on non-200 responses instead of a staleerr. Behavior is otherwise unchanged on the happy path.Test
gofmt -dclean.