From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Oleg Nesterov <oleg@redhat.com>
Subject: [GIT PULL] timer subsystem fixes
Date: Sun, 13 Sep 2026 10:25:33 +0200 [thread overview]
Message-ID: <aqZd_ZBZXumbuqAK@gmail.com> (raw)
Linus,
Please pull the latest timers/urgent Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-2026-09-13
for you to fetch changes up to c5dcb3aadc18d7b82ba64790721b005d18193d35:
Misc timer fixes:
- Fix clockevents replacement race when a broadcast
device is replaced which may trigger a BUG() crash
(朱恺乾 - Zhu Kaiqian)
- Fix potential timerqueue ordering bug when rearming
a queued timer with nonzero slack (Andrea Parri)
Thanks,
Ingo
------------------>
Andrea Parri (1):
hrtimer: Use hard expiry when updating timers on the same base
Thomas Gleixner (1):
tick/broadcast: Plug clockevents replacement race
kernel/time/clockevents.c | 33 ++++++++++++++++++++-------------
kernel/time/hrtimer.c | 15 +++++++++++----
kernel/time/tick-broadcast.c | 36 ++++++++++++++++++++++--------------
kernel/time/tick-internal.h | 2 ++
4 files changed, 55 insertions(+), 31 deletions(-)
next reply other threads:[~2026-09-13 8:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 8:25 Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-23 17:18 Ingo Molnar
2026-06-24 0:20 ` pr-tracker-bot
2026-06-07 5:07 Ingo Molnar
2026-06-07 20:43 ` pr-tracker-bot
2026-01-24 9:38 Ingo Molnar
2026-01-24 18:00 ` pr-tracker-bot
2025-11-23 7:58 Ingo Molnar
2025-11-23 16:26 ` pr-tracker-bot
2025-05-11 7:49 Ingo Molnar
2025-05-11 18:40 ` pr-tracker-bot
2025-05-04 7:26 Ingo Molnar
2025-05-04 7:34 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aqZd_ZBZXumbuqAK@gmail.com \
--to=mingo@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®