diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2024-08-04 17:50:16 +0200 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2024-08-04 17:50:16 +0200 |
commit | 61ca6c78295e242d4b681003112bfcdc54597489 (patch) | |
tree | 66974e4aa1946d2ea603bc69ef6b8110af350c73 /kernel/profile.c | |
parent | Merge tag 'sched-urgent-2024-08-04' of git://git.kernel.org/pub/scm/linux/ker... (diff) | |
parent | clocksource: Fix brown-bag boolean thinko in cs_watchdog_read() (diff) | |
download | linux-61ca6c78295e242d4b681003112bfcdc54597489.tar.xz linux-61ca6c78295e242d4b681003112bfcdc54597489.zip |
Merge tag 'timers-urgent-2024-08-04' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull timer fixes from Thomas Gleixner:
"Two fixes for the timer/clocksource code:
- The recent fix to make the take over of the broadcast timer more
reliable retrieves a per CPU pointer in preemptible context.
This went unnoticed in testing as some compilers hoist the access
into the non-preemotible section where the pointer is actually
used, but obviously compilers can rightfully invoke it where the
code put it.
Move it into the non-preemptible section right to the actual usage
side to cure it.
- The clocksource watchdog is supposed to emit a warning when the
retry count is greater than one and the number of retries reaches
the limit.
The condition is backwards and warns always when the count is
greater than one. Fixup the condition to prevent spamming dmesg"
* tag 'timers-urgent-2024-08-04' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
clocksource: Fix brown-bag boolean thinko in cs_watchdog_read()
tick/broadcast: Move per CPU pointer access into the atomic section
Diffstat (limited to 'kernel/profile.c')
0 files changed, 0 insertions, 0 deletions