Skip to content
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

Fix a MSAN issue in ext_authz due to max_request_bytes_ change #31897

Merged

Conversation

yanjunxiang-google
Copy link
Contributor

@yanjunxiang-google yanjunxiang-google commented Jan 18, 2024

There is a MSAN issue in ext_authz due to recently commit: #31437.
The error indicates use-of-uniniialized value of max_request_bytes_.

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

@yanjunxiang-google
Copy link
Contributor Author

/assign @agrawroh

Copy link
Contributor

@agrawroh agrawroh left a comment

Choose a reason for hiding this comment

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

Thanks! Is it worth adding a unit test?

@yanjunxiang-google
Copy link
Contributor Author

Thanks! Is it worth adding a unit test?

This change just initialize a variable to the default value. Not sure what test we need to add.

@ravenblackx ravenblackx self-assigned this Jan 19, 2024
@ravenblackx ravenblackx added the backport/review Request to backport to stable releases label Jan 19, 2024
@ravenblackx ravenblackx merged commit 2ad989f into envoyproxy:main Jan 19, 2024
53 checks passed
phlax pushed a commit to phlax/envoy that referenced this pull request Feb 6, 2024
@phlax
Copy link
Member

phlax commented Feb 6, 2024

backport added in #32211

@ravenblackx does this need to be backported further?

@ravenblackx
Copy link
Contributor

Description says the problem was introduced in #31437 which is not on any earlier branches, so I think 1.29 is far enough.

@phlax
Copy link
Member

phlax commented Feb 6, 2024

thanks - apologies for stupid qs - i was going through backports quickly

we should probably use some convention like /backport 1.28 etc to signify when to bp to - so its easier come release time to know what to do and whether resolved etc

@phlax phlax removed the backport/review Request to backport to stable releases label Feb 6, 2024
phlax pushed a commit that referenced this pull request Feb 6, 2024
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.

5 participants