-
Notifications
You must be signed in to change notification settings - Fork 564
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
Fixed segfault that may happen when data stream is opened during compaction #6619
Merged
mmedenjak
merged 4 commits into
redpanda-data:dev
from
mmaslankaprv:fix-seg-fault-when-compacting
Oct 4, 2022
Merged
Fixed segfault that may happen when data stream is opened during compaction #6619
mmedenjak
merged 4 commits into
redpanda-data:dev
from
mmaslankaprv:fix-seg-fault-when-compacting
Oct 4, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b54a494
to
5696bfc
Compare
When `_stream` list was iterated and modified in the same loop this invalidated the reference and caused segmentation fault. Using intrusive list move constructor instead and then updating the parent pointer in handler. Signed-off-by: Michal Maslanka <michal@redpanda.com>
Added custom move assignment operator to `segment_reader` as when assigned all the handlers must be updated with the parent pointer. Signed-off-by: Michal Maslanka <michal@redpanda.com>
Signed-off-by: Michal Maslanka <michal@redpanda.com>
5696bfc
to
f30c355
Compare
Signed-off-by: Michal Maslanka <michal@redpanda.com>
f30c355
to
57422a2
Compare
jcsp
approved these changes
Oct 4, 2022
Great catch. This feels like a signal that nothing in our integration tests is pushing compaction hard enough, as it wasn't reproducing there. |
dotnwat
approved these changes
Oct 4, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
move semantics bites again!
/backport v22.2.x |
Failed to run cherry-pick command. I executed the below command:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cover letter
Fixed two issues that happened when self compacting segment with open output file streams.
Modifying list when iterating over
When
_stream
list was iterated and modified in the same loop thisinvalidated the reference and caused segmentation fault. Using intrusive
list move constructor instead and then updating the parent pointer in
handler.
Missing custom assignment operator
Added custom move assignment operator to
segment_reader
as whenassigned all the handlers must be updated with the parent pointer.
Backtrace
Fixes #ISSUE-NUMBER, Fixes #ISSUE-NUMBER, ...
Backport Required
UX changes
Describe in plain language how this PR affects an end-user. What topic flags, configuration flags, command line flags, deprecation policies etc are added/changed.
Release notes