Skip to content

health-check: fix grpc health check multiple resets#13855

Closed
adisuissa wants to merge 1 commit intoenvoyproxy:masterfrom
adisuissa:fix_health_check_grpc
Closed

health-check: fix grpc health check multiple resets#13855
adisuissa wants to merge 1 commit intoenvoyproxy:masterfrom
adisuissa:fix_health_check_grpc

Conversation

@adisuissa
Copy link
Copy Markdown
Contributor

Commit Message: health-check: fix grpc health check multiple resets
Additional Description:
Multiple resets caused failure accessing request_encoder_ after the health check was already reset.
This PR verifies that request_encoder_ and client_ are valid before calling them.

Risk Level: Low - adding a check
Testing: Added fuzz test.
Docs Changes: None.
Release Notes: None.
Platform Specific Features: None.
Fixes fuzz test: 26848

Signed-off-by: Adi Suissa-Peleg adip@google.com

Signed-off-by: Adi Suissa-Peleg <adip@google.com>
@adisuissa
Copy link
Copy Markdown
Contributor Author

/assign @asraa @zasweq

Copy link
Copy Markdown
Contributor

@asraa asraa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Adi! Is this possible to trigger via traffic/integration test?

@mattklein123
Copy link
Copy Markdown
Member

qq: what do you mean by double reset? Two resets can't happen on the same stream. Is this a test framework bug?

@asraa
Copy link
Copy Markdown
Contributor

asraa commented Nov 2, 2020

Agreed, if so, I wonder if @zasweq has some input on how to modify the fuzzer for this flow

@zasweq
Copy link
Copy Markdown
Contributor

zasweq commented Nov 2, 2020

Hey everyone, thanks for looking at this! Investigating now :)!

@adisuissa
Copy link
Copy Markdown
Contributor Author

#13780 might provide a better solution.
Closing this PR until further investigation.

@adisuissa adisuissa closed this Nov 3, 2020
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.

4 participants