From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Waiman Long <longman@redhat.com>
Subject: [GIT PULL] timer subsystem fixes
Date: Sun, 4 May 2025 09:26:08 +0200 [thread overview]
Message-ID: <aBcWkIOBqkKG8lH-@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-05-04
# HEAD: 7aeb1538be5df3efa1d799e5428ac3a0ae802293 vdso: Reject absolute relocations during build
Misc fixes:
- Fix time keeping bugs in CLOCK_MONOTONIC_COARSE clocks
- Work around and reject absolute relocations into vDSO code that
GCC erroneously emits in certain arm64 build environments
Thanks,
Ingo
------------------>
Thomas Gleixner (1):
timekeeping: Prevent coarse clocks going backwards
Thomas Weißschuh (2):
arm64: vdso: Work around invalid absolute relocations from GCC
vdso: Reject absolute relocations during build
arch/arm64/include/asm/vdso/gettimeofday.h | 13 ++++++++
include/linux/timekeeper_internal.h | 8 +++--
kernel/time/timekeeping.c | 50 +++++++++++++++++++++++++-----
kernel/time/vsyscall.c | 4 +--
lib/vdso/Makefile.include | 6 ++++
5 files changed, 68 insertions(+), 13 deletions(-)
next reply other threads:[~2025-05-04 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-04 7:26 Ingo Molnar [this message]
2025-05-04 7:34 ` [GIT PULL] timer subsystem fixes Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2025-05-11 7:49 Ingo Molnar
2025-05-11 18:40 ` pr-tracker-bot
2025-11-23 7:58 Ingo Molnar
2025-11-23 16:26 ` pr-tracker-bot
2026-01-24 9:38 Ingo Molnar
2026-01-24 18:00 ` 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=aBcWkIOBqkKG8lH-@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@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