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

Cluster: Don't crash when adding a forgotten node to blacklist twice #12702

Merged

Conversation

zuiderkwast
Copy link
Contributor

Fixes #12701

This is defensive code to avoid the problem. I haven't reproduced the crash though.

@madolson madolson merged commit 8d67595 into redis:unstable Oct 31, 2023
13 checks passed
@zuiderkwast zuiderkwast deleted the forgotten-node-already-in-blacklist-fix branch October 31, 2023 16:18
@oranagra oranagra added the release-notes indication that this issue needs to be mentioned in the release notes label Nov 1, 2023
@oranagra oranagra changed the title Don't crash when adding a forgotten node to blacklist twice Cluster: Don't crash when adding a forgotten node to blacklist twice Nov 1, 2023
oranagra pushed a commit to oranagra/redis that referenced this pull request Nov 1, 2023
)

Add a defensive checks to prevent double freeing a node from the cluster blacklist.

(cherry picked from commit 8d67595)
@oranagra oranagra mentioned this pull request Nov 1, 2023
oranagra pushed a commit that referenced this pull request Nov 1, 2023
Add a defensive checks to prevent double freeing a node from the cluster blacklist.

(cherry picked from commit 8d67595)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes indication that this issue needs to be mentioned in the release notes
Projects
Development

Successfully merging this pull request may close these issues.

[CRASH] Cluster CLUSTERMSG_EXT_TYPE_FORGOTTEN_NODE
4 participants