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

[C++] Fixed handling of canceled timer events on NegativeAcksTracker #6272

Merged
merged 1 commit into from
Feb 10, 2020

Conversation

merlimat
Copy link
Contributor

@merlimat merlimat commented Feb 8, 2020

Motivation

When handling a "timer cancelled" event, we cannot lock the mutex since the object itself might already be destroyed.

This causes potentially a memory corruption/segfault.

@merlimat merlimat added type/bug The PR fixed a bug or issue reported a bug component/c++ release/2.4.3 release/2.5.1 labels Feb 8, 2020
@merlimat merlimat added this to the 2.6.0 milestone Feb 8, 2020
@merlimat merlimat self-assigned this Feb 8, 2020
@jiazhai jiazhai merged commit 54a5195 into apache:master Feb 10, 2020
tuteng pushed a commit to AmateurEvents/pulsar that referenced this pull request Feb 23, 2020
…pache#6272)

When handling a "timer cancelled" event, we cannot lock the mutex since the object itself might already be destroyed.

This causes potentially a memory corruption/segfault.
tuteng pushed a commit to AmateurEvents/pulsar that referenced this pull request Mar 21, 2020
…pache#6272)

When handling a "timer cancelled" event, we cannot lock the mutex since the object itself might already be destroyed.

This causes potentially a memory corruption/segfault.

(cherry picked from commit 54a5195)
tuteng pushed a commit that referenced this pull request Apr 6, 2020
…6272)

When handling a "timer cancelled" event, we cannot lock the mutex since the object itself might already be destroyed.

This causes potentially a memory corruption/segfault.

(cherry picked from commit 54a5195)
tuteng pushed a commit that referenced this pull request Apr 13, 2020
…6272)

When handling a "timer cancelled" event, we cannot lock the mutex since the object itself might already be destroyed.

This causes potentially a memory corruption/segfault.

(cherry picked from commit 54a5195)
jiazhai pushed a commit to jiazhai/pulsar that referenced this pull request May 18, 2020
…pache#6272)

When handling a "timer cancelled" event, we cannot lock the mutex since the object itself might already be destroyed.

This causes potentially a memory corruption/segfault.
(cherry picked from commit 54a5195)
huangdx0726 pushed a commit to huangdx0726/pulsar that referenced this pull request Aug 24, 2020
…pache#6272)

When handling a "timer cancelled" event, we cannot lock the mutex since the object itself might already be destroyed.

This causes potentially a memory corruption/segfault.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release/2.4.3 release/2.5.1 type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants