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

v1.18: gossip: do not allow duplicate proofs for incorrect shred versions (backport of #1931) #1940

Merged
merged 1 commit into from
Jul 3, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jul 1, 2024

Problem

Nodes that do not participate in a cluster restart can have old shreds with a previous shred version.
Upon restart they will create duplicate proofs using this old shred version and newly received shreds and propagate them to the rest of the cluster.

Summary of Changes

Disallow creation and consumption of duplicate proofs involving shreds with incorrect shred versions


This is an automatic backport of pull request #1931 done by [Mergify](https://mergify.com).

@mergify mergify bot requested a review from a team as a code owner July 1, 2024 16:06
…1931)

* gossip: do not allow duplicate proofs for incorrect shred versions

* pr feedback: refactor test function to take shred_version

(cherry picked from commit 69ea21e)
Copy link

@steviez steviez left a comment

Choose a reason for hiding this comment

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

LGTM - I think we should ship this for v1.18 in addition to the v2.0 BP that already landed. Same as before, this will prevent the creation of duplicate proofs where part of the proof is a pre-restart shred and should be considered invalid

Copy link

@t-nelson t-nelson left a comment

Choose a reason for hiding this comment

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

we doing the blockstore cleanup one too?

@AshwinSekar AshwinSekar merged commit 292093e into v1.18 Jul 3, 2024
35 checks passed
@AshwinSekar AshwinSekar deleted the mergify/bp/v1.18/pr-1931 branch July 3, 2024 00:04
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.

3 participants