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.

Sign up for GitHub

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

Jump to bottom

Fix possible stack-use-after-return in LimitReadBuffer #45203

Merged
merged 2 commits into from
Jan 12, 2023
Merged

Fix possible stack-use-after-return in LimitReadBuffer #45203

merged 2 commits into from
Jan 12, 2023

Conversation

Avogar
Copy link
Member

@Avogar Avogar commented Jan 11, 2023

Changelog category (leave one):

  • Not for changelog (changelog entry is not required)

Closes #45199

@robot-clickhouse robot-clickhouse added the pr-not-for-changelog This PR should not be mentioned in the changelog label Jan 11, 2023
@Avogar Avogar changed the title Fix pissible stack-use-after-return in LimitReadBuffer Fix possible stack-use-after-return in LimitReadBuffer Jan 11, 2023
@nickitat nickitat self-assigned this Jan 11, 2023
@qoega
Copy link
Member

qoega commented Jan 12, 2023

@qoega qoega merged commit 07b8abf into master Jan 12, 2023
@qoega qoega deleted the Avogar-patch-1 branch January 12, 2023 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@nickitat nickitat nickitat approved these changes

@alexey-milovidov alexey-milovidov alexey-milovidov approved these changes

Assignees

@nickitat nickitat

Labels
pr-not-for-changelog This PR should not be mentioned in the changelog
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

stack-use-after-return in LimitReadBuffer
5 participants
@Avogar @qoega @nickitat @alexey-milovidov @robot-clickhouse