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

i#6938 sched migrate: Make initial_cur_time atomic #7043

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

derekbruening
Copy link
Contributor

Fixes a race in the drmemtrace scheduler by making output_info_t.initial_cur_time atomic.

Tested on ThreadSanitizer on the internal test where this was first reported.

Issue: #6938

Fixes a race in the drmemtrace scheduler by making
output_info_t.initial_cur_time atomic.

Tested on ThreadSanitizer on the internal test where this was first
reported.

Issue: #6938
@edeiana
Copy link
Contributor

edeiana commented Oct 16, 2024

ci-aarchxx / aarch64-precommit code_api|api.startstop is failing, but it seems unrelated.
I'm re-running that ci.

@derekbruening
Copy link
Contributor Author

ci-aarchxx / aarch64-precommit code_api|api.startstop is failing, but it seems unrelated. I'm re-running that ci.

Thanks, startstop is probably #6928.

@derekbruening derekbruening merged commit 36e7538 into master Oct 16, 2024
17 checks passed
@derekbruening derekbruening deleted the i6938-init-time-lock branch October 16, 2024 04:47
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.

2 participants