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

mpool: fix: data race when adding messages #10771

Closed
wants to merge 1 commit into from

Conversation

snissn
Copy link
Contributor

@snissn snissn commented Apr 27, 2023

Related Issues

#10755

Proposed Changes

add RLock around getStateNonce calls

Additional Info

replaces #10758

Checklist

Before you mark the PR ready for review, please make sure that:

  • Commits have a clear commit message.
  • PR title is in the form of of <PR type>: <area>: <change being made>
    • example: fix: mempool: Introduce a cache for valid signatures
    • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
    • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
  • New features have usage guidelines and / or documentation updates in
  • Tests exist for new functionality or change in behavior
  • CI is green

@snissn snissn requested a review from a team as a code owner April 27, 2023 02:36
@snissn snissn linked an issue Apr 27, 2023 that may be closed by this pull request
@snissn snissn requested a review from Stebalien April 27, 2023 02:36
@Stebalien
Copy link
Member

Ok, I think I messed up. I was probably looking at release/1.22.0, not master. I'm now looking at resolveToKey and see that we're using an LRU cache (from a PR that I definitely reviewed... #10561).

So maybe there isn't a race? But I don't trust myself anymore.

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.

[mpool] data race when adding messages
2 participants