-
Notifications
You must be signed in to change notification settings - Fork 7
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
Crash handler recursion protection - Fix #139
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When exiting through the longjmp path, we should reset the depth instead of decrementing.
r1viollet
force-pushed
the
r1viollet/fix_crash_handler_protection
branch
from
October 16, 2024 08:08
d3311d2
to
567af10
Compare
r1viollet
commented
Oct 16, 2024
@@ -458,7 +458,7 @@ void StackWalker::checkFault(ProfiledThread* thrd) { | |||
VMThread *vm_thread = VMThread::current(); | |||
if (vm_thread != NULL && sameStack(vm_thread->exception(), &vm_thread)) { | |||
if (thrd) { | |||
thrd->exitCrashHandler(); | |||
thrd->resetCrashHandler(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the main change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a comment here about why the reset needs to be done here?
🔧 Report generated by pr-comment-scanbuild Scan-Build Report
Bug Summary
Reports
|
jbachorik
approved these changes
Oct 23, 2024
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?:
When exiting through the longjmp path, we should reset the depth instead of decrementing.
There were a lot of warnings in the CI. I fixed the most obvious ones.
The PR can be reviewed with separate commits.
Motivation:
Jaroslav witnessed a crash in the safe access function (meaning we were not preventing the safe access crashes).
Additional Notes:
How to test the change?:
I have not been able to reproduce as of now.
For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance
.Unsure? Have a question? Request a review!