-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
txn: Fix data race of checking and exiting fair locking concurrently in LockKeys #42635
txn: Fix data race of checking and exiting fair locking concurrently in LockKeys #42635
Conversation
Signed-off-by: MyonKeminta <MyonKeminta@users.noreply.github.com>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Signed-off-by: MyonKeminta <MyonKeminta@users.noreply.github.com>
/merge |
This pull request has been accepted and is ready to merge. Commit hash: af1eefb
|
/test unit-test |
What problem does this PR solve?
Issue Number: close #42615
Requires: tikv/client-go#749
Problem Summary:
The
LockKeys
functions in txn_driver.go can be called concurrently in some case. However we added some fair locking related logic here, which is not protected by the mutex that's locked inLockKeys
of client-go: if locking more than one key, exit fair locking mode.What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.
Release note not needed since the bug is just introduced in 7.0