Skip to content

Cherrypick 1.4.2#128

Merged
howardjohn merged 3 commits intoistio:release-1.4from
howardjohn:14/cp-142
Dec 10, 2019
Merged

Cherrypick 1.4.2#128
howardjohn merged 3 commits intoistio:release-1.4from
howardjohn:14/cp-142

Conversation

@howardjohn
Copy link
Member

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md

Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

htuch and others added 3 commits December 10, 2019 10:10
Fixes oss-fuzz issue
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18431.

Risk level: Low (no functional change).
Testing: Additional unit and integration tests added that cover the
  :method header overflow case and adjacent behaviors. Corpus entry
  added.

Signed-off-by: Harvey Tuch <htuch@google.com>
(cherry picked from commit f071242)
This can happen during certain early reply cases in the HCM
when an encoder filter tries to lookup the cached route/cluster.

Signed-off-by: Matt Klein <mklein@lyft.com>
(cherry picked from commit e9951ac)
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
(cherry picked from commit 6d525c6)
@googlebot
Copy link

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@howardjohn
Copy link
Member Author

DO NOT press merge.

@howardjohn howardjohn merged commit 710d256 into istio:release-1.4 Dec 10, 2019
howardjohn pushed a commit that referenced this pull request Mar 3, 2020
Description: Remove empty slices off the end of buffers after calls to OwnedImpl::commit. The slices reserved when OwnedImpl::reserve is called will sit unused in cases where the 0 bytes are commited, for example, when socket read returns 0 bytes EAGAIN. Trapped slices act like a memory leak until there is a successful read or the socket is closed.
Risk Level: low
Testing: unit
Docs Changes: n/a
Release Notes: n/a

Signed-off-by: Antonio Vicente <avd@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Yangmin Zhu <ymzhu@google.com>
brian-avery pushed a commit that referenced this pull request Jun 30, 2020
Description: Remove empty slices off the end of buffers after calls to OwnedImpl::commit. The slices reserved when OwnedImpl::reserve is called will sit unused in cases where the 0 bytes are commited, for example, when socket read returns 0 bytes EAGAIN. Trapped slices act like a memory leak until there is a successful read or the socket is closed.
Risk Level: low
Testing: unit
Docs Changes: n/a
Release Notes: n/a

Signed-off-by: Antonio Vicente <avd@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Yangmin Zhu <ymzhu@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants