storage: fix reverse scan check memory locks (#11447)

[ti-srebot]

cherry-pick #11447 to release-5.0
You can switch your code base to this Pull Request by using git-extras:

# In tikv repo:
git pr https://github.com/tikv/tikv/pull/11453

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tikv.git pr/11453:release-5.0-4429fdcc7ef5

---

Signed-off-by: youjiali1995 zlwgx1023@gmail.com

What problem does this PR solve?

Issue Number:close #11440

Problem Summary:

Reverse scan's start_key is greater than end_key, but storage always uses [start_key, end_key) to check memory locks.

What is changed and how it works?

What's Changed:

Swap start_key and end_key if is a reverse scan.

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Unit test

Side effects

Release note

Fix the issue that reverse scan can't detect memory locks and may read stale data.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• sticnarf
• youjiali1995

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-srebot]

/run-all-tests

[ti-srebot]

@youjiali1995 you're already a collaborator in bot's repo.

[Little-Wallace]

/test

[zhouqiang-cl]

/merge

[ti-chi-bot]

@zhouqiang-cl: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 98990a0

[ti-chi-bot]

@ti-srebot: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.