Skip to content

Fix potential race condition in the sync manager - gossip syncer registration #9891

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

Closed

Conversation

ziggie1984
Copy link
Collaborator

@ziggie1984 ziggie1984 commented Jun 3, 2025

Fix a potential race condition when adding/removing the gossip_syncer to the sync_manager described below ...

Copy link
Contributor

coderabbitai bot commented Jun 3, 2025

Important

Review skipped

Auto reviews are limited to specific labels.

🏷️ Labels to auto review (1)
  • llm-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@ziggie1984 ziggie1984 self-assigned this Jun 3, 2025
@ziggie1984
Copy link
Collaborator Author

Addresses issues found in: #9886

//
// NOTE: We need to do this synchronously to make sure a gossip peer
// is registered before we signal that the peer is active because
// otherwise the is a race which can happen that we try to remove the
Copy link
Member

Choose a reason for hiding this comment

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

what is the race?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

what guarantees that the peer does not flake and we shutdown before the gossiper is registered:

Currently we try to register the syncer async here:

p.initGossipSync()

However we could already hit the disconnect case here:

because we signal ready here:

lnd/server.go

Line 4597 in 7e44422

close(ready)

and could hit the removal of the gossiper here:

lnd/server.go

Line 4653 in 7e44422

s.authGossiper.PruneSyncState(p.PubKey())

Copy link
Collaborator Author

@ziggie1984 ziggie1984 Jun 3, 2025

Choose a reason for hiding this comment

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

no guarantee that the addition is before the removal or ?

Copy link
Member

Choose a reason for hiding this comment

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

yea make sense - the only thing is whether this initGossipSync will ever be blocking or not?

Copy link
Collaborator Author

@ziggie1984 ziggie1984 Jun 4, 2025

Choose a reason for hiding this comment

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

by blocking you mean blocking for a short period of time ? I mean depends on the busyness of the sync_manager or, I think that is why we need to make it sync in the first place because we cannot be sure that it registers in time before the peer might go offline.

Copy link
Member

Choose a reason for hiding this comment

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

blocking as in whether it will delay the startup or even create a deadlock somewhere - previously it's async so I think it's fine, now it's sync, and I've noticed a few places where the initGossipSync will wait for done signal.

and what happens before if the registration is not finished before the removal of the gossiper? i think it will be a noop? will the new registration still register the syncer afterwards?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

ok will double check.

@saubyk saubyk added this to the v0.19.1 milestone Jun 3, 2025
@saubyk saubyk linked an issue Jun 3, 2025 that may be closed by this pull request
@saubyk saubyk modified the milestones: v0.19.1, v0.19.2 Jun 3, 2025
@ziggie1984 ziggie1984 changed the title memory leak in peer connection Fix potential race condition in the sync manager - gossip syncer registration Jun 3, 2025
@ziggie1984 ziggie1984 marked this pull request as ready for review June 3, 2025 19:48
@saubyk saubyk modified the milestones: v0.19.2, v0.20.0 Jun 5, 2025
@saubyk saubyk added this to lnd v0.20 Jun 5, 2025
@saubyk saubyk moved this to In review in lnd v0.20 Jun 5, 2025
@lightninglabs-deploy
Copy link

@ziggie1984, remember to re-request review from reviewers when ready

@ziggie1984
Copy link
Collaborator Author

My first analysis was wrong I made here:
#9891 (comment)

We always make sure before we remove the gossiper here:

lnd/server.go

Line 4661 in a5c4a7c

s.authGossiper.PruneSyncState(p.PubKey())

that the peer and therefore the waitGroupCounter has reached zero:

lnd/server.go

Line 4640 in a5c4a7c

p.WaitForDisconnect(ready)

especially here:

p.cg.WgWait()

so it would never be the case that we remove a gossiper before it was added.

Thanks for your careful analysis @yyforyongyu 🙏

@ziggie1984 ziggie1984 closed this Jun 16, 2025
@github-project-automation github-project-automation bot moved this from In review to Done in lnd v0.20 Jun 16, 2025
@ziggie1984 ziggie1984 removed this from the v0.20.0 milestone Jun 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants