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>
Subject: [GIT PULL] timer subsystem fix
Date: Sun, 15 Mar 2026 04:30:56 +0100 [thread overview]
Message-ID: <abYn8FA9eRNqhAwC@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-03-15
for you to fetch changes up to 755a648e78f12574482d4698d877375793867fa1:
Fix function tracer recursion bug by marking jiffies_64_to_clock_t()
notrace.
Thanks,
Ingo
------------------>
Steven Rostedt (1):
time/jiffies: Mark jiffies_64_to_clock_t() notrace
kernel/time/time.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/time.c b/kernel/time/time.c
index 36fd2313ae7e..0d832317d576 100644
--- a/kernel/time/time.c
+++ b/kernel/time/time.c
@@ -697,7 +697,7 @@ EXPORT_SYMBOL(clock_t_to_jiffies);
*
* Return: jiffies_64 value converted to 64-bit "clock_t" (CLOCKS_PER_SEC)
*/
-u64 jiffies_64_to_clock_t(u64 x)
+notrace u64 jiffies_64_to_clock_t(u64 x)
{
#if (TICK_NSEC % (NSEC_PER_SEC / USER_HZ)) == 0
# if HZ < USER_HZ
next reply other threads:[~2026-03-15 3:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 3:30 Ingo Molnar [this message]
2026-03-15 18:47 ` [GIT PULL] timer subsystem fix pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2026-03-29 5:27 Ingo Molnar
2026-03-29 17:29 ` pr-tracker-bot
2026-03-08 0:49 Ingo Molnar
2026-03-08 1:23 ` pr-tracker-bot
2026-01-18 10:05 Ingo Molnar
2026-01-19 13:54 ` pr-tracker-bot
2025-11-15 9:13 Ingo Molnar
2025-11-15 18:26 ` pr-tracker-bot
2025-09-14 9:34 Ingo Molnar
2025-09-14 15:43 ` pr-tracker-bot
2025-09-07 10:35 Ingo Molnar
2025-09-07 15:32 ` pr-tracker-bot
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=abYn8FA9eRNqhAwC@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=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