Skip to content

Conversation

@mattcaswell
Copy link
Member

If a mem allocation failed we would ignore it. This commit fixes it to
always check.

If a mem allocation failed we would ignore it. This commit fixes it to
always check.
Copy link
Contributor

@richsalz richsalz left a comment

Choose a reason for hiding this comment

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

for any branches you care to do so.

levitte pushed a commit that referenced this pull request Mar 12, 2018
If a mem allocation failed we would ignore it. This commit fixes it to
always check.

Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from #5596)

(cherry picked from commit 4718f44)
levitte pushed a commit that referenced this pull request Mar 12, 2018
If a mem allocation failed we would ignore it. This commit fixes it to
always check.

Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from #5596)

(cherry picked from commit 4718f44)
@mattcaswell
Copy link
Member Author

Pushed. It cherry-picked cleanly to 1.1.0 and 1.0.2 so I pushed to both of those too.

levitte pushed a commit that referenced this pull request Mar 12, 2018
If a mem allocation failed we would ignore it. This commit fixes it to
always check.

Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from #5596)
makr pushed a commit to makr/openssl that referenced this pull request Mar 14, 2018
If a mem allocation failed we would ignore it. This commit fixes it to
always check.

Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from openssl#5596)

(cherry picked from commit 4718f44)
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.

2 participants