[release/10.0] Add missing HAVE_CLOCK_MONOTONIC to config.h.in#124121
Open
Copilot wants to merge 1 commit intorelease/10.0from
Open
[release/10.0] Add missing HAVE_CLOCK_MONOTONIC to config.h.in#124121Copilot wants to merge 1 commit intorelease/10.0from
Copilot wants to merge 1 commit intorelease/10.0from
Conversation
github-actions
bot
added
the
needs-area-label
jkotas
added
area-System.Threading
and removed
needs-area-label
Copilot stopped work on behalf of
jkotas due to an error
February 7, 2026 02:02
Member
|
@copilot Try again |
Contributor
Author
I've created commit 4f20351 with the fix (adding HAVE_CLOCK_MONOTONIC to config.h.in) based on release/10.0, and updated the PR description to follow the servicing template. However, I cannot force-push due to incompatible branch histories (origin/copilot branch is based on main, but needs to be based on release/10.0). The PR base branch also needs to be manually changed from |
Copilot stopped work on behalf of
jkotas due to an error
February 7, 2026 02:28
jkotas
force-pushed
the
copilot/backport-runtime-pr-124086
branch
from
1531bd9 to
cdc557a
Compare
Fixes issue #123950 where Task.Delay freezes when system time jumps backwards on .NET 10 Linux - a regression from .NET 8 and 9. The root cause was a missing `#cmakedefine01 HAVE_CLOCK_MONOTONIC` directive in `src/coreclr/pal/src/config.h.in`. While CMake was successfully detecting monotonic clock support, the configuration value was never propagated to the generated config.h header. This caused the runtime to fall back to wall-clock time (CLOCK_REALTIME) instead of monotonic clocks (CLOCK_MONOTONIC), making timing operations vulnerable to system time adjustments. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jkotas <6668460+jkotas@users.noreply.github.com>
dotnet-policy-service
bot
added
the
linkable-framework
jkotas
changed the title
stephentoub
approved these changes
Feb 7, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Backports the fix for a .NET 10 Linux regression where timing operations (e.g., Task.Delay) can hang indefinitely if the system clock is adjusted backwards, by ensuring CMake’s monotonic clock detection is propagated into the generated PAL config header.
Changes:
- Add the missing
#cmakedefine01 HAVE_CLOCK_MONOTONICto the PALconfig.h.intemplate soHAVE_CLOCK_MONOTONICis correctly emitted intoconfig.h.
3 tasks
This file contains hidden or 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
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.
Backport of #124086 to release/10.0
Customer Impact
Task.Delay and other timing operations freeze indefinitely when system time is adjusted backwards on Linux in .NET 10. Reported by two different customers.
Regression
Add missing
#cmakedefine01 HAVE_CLOCK_MONOTONICtosrc/coreclr/pal/src/config.h.in. While CMake successfully detects monotonic clock support, the configuration value is never propagated to the generated config.h header. This causes the runtime to incorrectly fall back to wall-clock time (CLOCK_REALTIME) instead of using monotonic clocks (CLOCK_MONOTONIC),Testing
Customer confirmed the issue is fixed using private build
Risk
Minimal - one-line CMake configuration fix restoring .NET 8/9 behavior.