Skip to content

branch-4.0: [Fix](Exception) Fix potential use-after-free because Exception::to_string is not thread safe #59558 - #59598

Merged
yiguolei merged 1 commit into
branch-4.0from
auto-pick-59558-branch-4.0
Jan 7, 2026
Merged

branch-4.0: [Fix](Exception) Fix potential use-after-free because Exception::to_string is not thread safe #59558#59598
yiguolei merged 1 commit into
branch-4.0from
auto-pick-59558-branch-4.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #59558

…string` is not thread safe (#59558)
### What problem does this PR solve?
Problem Summary:
`Exception::to_string()` may by accessed concurrently in the following
situation:
- thread A and thread B access the same `DorisCallOnce` object
- An Exception `e` is throw when thread A is calling
`DorisCallOnce::call` and `e` is thrown to thread A
- `e` will be also thrown to thread B later by DorisCallOnce
- thread A and thread B access `Exception::to_string()` concurrently
This may cause use-after-free due to the assignment of `_cache_string`
in `Exception::to_string`
Considering that `Exception` should not be frequently used, this PR
construct `_cache_string` in constructor `Exception::Exception` rather
than lazily creating it. This can avoid additional unnessary
synchronazation.
### Release note
None
### Check List (For Author)
- Test <!-- At least one of them must be included. -->
- [ ] Regression test
- [ ] Unit Test
- [ ] Manual test (add detailed scripts or steps below)
- [ ] No need to test or manual test. Explain why:
- [ ] This is a refactor/code format and no logic has been changed.
- [ ] Previous test can cover this change.
- [ ] No code files have been changed.
- [ ] Other reason <!-- Add your reason? -->
- Behavior changed:
- [ ] No.
- [ ] Yes. <!-- Explain the behavior change -->
- Does this need documentation?
- [ ] No.
- [ ] Yes. <!-- Add document PR link here. eg:
apache/doris-website#1214 -->
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR
should merge into -->
@Thearas

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@Thearas

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 100.00% (8/8) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage53.28% (18674/35049)
Line Coverage39.10% (173031/442531)
Region Coverage33.79% (133714/395739)
Branch Coverage34.77% (57829/166335)

@github-actions

Copy link
Copy Markdown
ContributorAuthor

PR approved by at least one committer and no changes requested.

@github-actionsgithub-actionsBot added approved Indicates a PR has been approved by one committer. reviewed labels Jan 7, 2026
@github-actions

Copy link
Copy Markdown
ContributorAuthor

PR approved by anyone and no changes requested.

@yiguolei
yiguolei merged commit 19fa931 into branch-4.0Jan 7, 2026
24 of 26 checks passed
@github-actions
github-actionsBot deleted the auto-pick-59558-branch-4.0 branch January 7, 2026 10:07
ybtsdst pushed a commit to ybtsdst/doris that referenced this pull request Feb 27, 2026
…ception::to_string` is not thread safe apache#59558 (apache#59598)
Cherry-picked from apache#59558
Co-authored-by: bobhan1 <baohan@selectdb.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approvedIndicates a PR has been approved by one committer.reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@Thearas@hello-stephen@yiguolei@dataroaring@bobhan1