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>,
Andrew Morton <akpm@linux-foundation.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>
Subject: [GIT PULL] timer subsystem fixes
Date: Sun, 23 Nov 2025 08:58:53 +0100 [thread overview]
Message-ID: <aSK-vTe6r5621zon@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-2025-11-23
# HEAD: 20739af07383e6eb1ec59dcd70b72ebfa9ac362c timers: Fix NULL function pointer race in timer_shutdown_sync()
Miscellaneous fixes:
- Fix a race in timer->function clearing in timer_shutdown_sync()
- Fix a timekeeper sysfs-setup resource leak in error paths
- Fix the NOHZ report_idle_softirq() syslog rate-limiting
logic to have no side effects on the return value
Thanks,
Ingo
------------------>
Malaya Kumar Rout (1):
timekeeping: Fix resource leak in tk_aux_sysfs_init() error paths
Wen Yang (1):
tick/sched: Fix bogus condition in report_idle_softirq()
Yipeng Zou (1):
timers: Fix NULL function pointer race in timer_shutdown_sync()
kernel/time/tick-sched.c | 11 +++++------
kernel/time/timekeeping.c | 21 ++++++++++++---------
kernel/time/timer.c | 7 ++++---
3 files changed, 21 insertions(+), 18 deletions(-)
next reply other threads:[~2025-11-23 7:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 7:58 Ingo Molnar [this message]
2025-11-23 16:26 ` [GIT PULL] timer subsystem fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
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-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=aSK-vTe6r5621zon@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.