From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: VDSO: fix coarse clock monotonicity regression
Date: Mon, 10 Aug 2015 16:48:16 +0100 [thread overview]
Message-ID: <20150810154815.GH1604@arm.com> (raw)
In-Reply-To: <1439221592-31875-1-git-send-email-nathan_lynch@mentor.com>
On Mon, Aug 10, 2015 at 04:46:32PM +0100, Nathan Lynch wrote:
> Since 906c55579a63 ("timekeeping: Copy the shadow-timekeeper over the
> real timekeeper last") it has become possible on ARM to:
>
> - Obtain a CLOCK_MONOTONIC_COARSE or CLOCK_REALTIME_COARSE timestamp
> via syscall.
> - Subsequently obtain a timestamp for the same clock ID via VDSO which
> predates the first timestamp (by one jiffy).
>
> This is because ARM's update_vsyscall is deriving the coarse time
> using the __current_kernel_time interface, when it should really be
> using the timekeeper object provided to it by the timekeeping core.
> It happened to work before only because __current_kernel_time would
> access the same timekeeper object which had been passed to
> update_vsyscall. This is no longer the case.
>
> Signed-off-by: Nathan Lynch <nathan_lynch@mentor.com>
> ---
>
> Changes since v1:
> - Add u32 cast to nsec calculation.
Acked-by: Will Deacon <will.deacon@arm.com>
Probably best sticking it into Russell's patch system with a Cc stable
in case it doesn't make it for 4.2.
Will
> arch/arm/kernel/vdso.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm/kernel/vdso.c b/arch/arm/kernel/vdso.c
> index efe17dd9b921..54a5aeab988d 100644
> --- a/arch/arm/kernel/vdso.c
> +++ b/arch/arm/kernel/vdso.c
> @@ -296,7 +296,6 @@ static bool tk_is_cntvct(const struct timekeeper *tk)
> */
> void update_vsyscall(struct timekeeper *tk)
> {
> - struct timespec xtime_coarse;
> struct timespec64 *wtm = &tk->wall_to_monotonic;
>
> if (!cntvct_ok) {
> @@ -308,10 +307,10 @@ void update_vsyscall(struct timekeeper *tk)
>
> vdso_write_begin(vdso_data);
>
> - xtime_coarse = __current_kernel_time();
> vdso_data->tk_is_cntvct = tk_is_cntvct(tk);
> - vdso_data->xtime_coarse_sec = xtime_coarse.tv_sec;
> - vdso_data->xtime_coarse_nsec = xtime_coarse.tv_nsec;
> + vdso_data->xtime_coarse_sec = tk->xtime_sec;
> + vdso_data->xtime_coarse_nsec = (u32)(tk->tkr_mono.xtime_nsec >>
> + tk->tkr_mono.shift);
> vdso_data->wtm_clock_sec = wtm->tv_sec;
> vdso_data->wtm_clock_nsec = wtm->tv_nsec;
>
> --
> 2.1.0
>
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Nathan Lynch <nathan_lynch@mentor.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Russell King <linux@arm.linux.org.uk>,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: VDSO: fix coarse clock monotonicity regression
Date: Mon, 10 Aug 2015 16:48:16 +0100 [thread overview]
Message-ID: <20150810154815.GH1604@arm.com> (raw)
In-Reply-To: <1439221592-31875-1-git-send-email-nathan_lynch@mentor.com>
On Mon, Aug 10, 2015 at 04:46:32PM +0100, Nathan Lynch wrote:
> Since 906c55579a63 ("timekeeping: Copy the shadow-timekeeper over the
> real timekeeper last") it has become possible on ARM to:
>
> - Obtain a CLOCK_MONOTONIC_COARSE or CLOCK_REALTIME_COARSE timestamp
> via syscall.
> - Subsequently obtain a timestamp for the same clock ID via VDSO which
> predates the first timestamp (by one jiffy).
>
> This is because ARM's update_vsyscall is deriving the coarse time
> using the __current_kernel_time interface, when it should really be
> using the timekeeper object provided to it by the timekeeping core.
> It happened to work before only because __current_kernel_time would
> access the same timekeeper object which had been passed to
> update_vsyscall. This is no longer the case.
>
> Signed-off-by: Nathan Lynch <nathan_lynch@mentor.com>
> ---
>
> Changes since v1:
> - Add u32 cast to nsec calculation.
Acked-by: Will Deacon <will.deacon@arm.com>
Probably best sticking it into Russell's patch system with a Cc stable
in case it doesn't make it for 4.2.
Will
> arch/arm/kernel/vdso.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm/kernel/vdso.c b/arch/arm/kernel/vdso.c
> index efe17dd9b921..54a5aeab988d 100644
> --- a/arch/arm/kernel/vdso.c
> +++ b/arch/arm/kernel/vdso.c
> @@ -296,7 +296,6 @@ static bool tk_is_cntvct(const struct timekeeper *tk)
> */
> void update_vsyscall(struct timekeeper *tk)
> {
> - struct timespec xtime_coarse;
> struct timespec64 *wtm = &tk->wall_to_monotonic;
>
> if (!cntvct_ok) {
> @@ -308,10 +307,10 @@ void update_vsyscall(struct timekeeper *tk)
>
> vdso_write_begin(vdso_data);
>
> - xtime_coarse = __current_kernel_time();
> vdso_data->tk_is_cntvct = tk_is_cntvct(tk);
> - vdso_data->xtime_coarse_sec = xtime_coarse.tv_sec;
> - vdso_data->xtime_coarse_nsec = xtime_coarse.tv_nsec;
> + vdso_data->xtime_coarse_sec = tk->xtime_sec;
> + vdso_data->xtime_coarse_nsec = (u32)(tk->tkr_mono.xtime_nsec >>
> + tk->tkr_mono.shift);
> vdso_data->wtm_clock_sec = wtm->tv_sec;
> vdso_data->wtm_clock_nsec = wtm->tv_nsec;
>
> --
> 2.1.0
>
next prev parent reply other threads:[~2015-08-10 15:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 2:03 [PATCH 0/2] fix vdso coarse clock monotonicity regressions Nathan Lynch
2015-08-08 2:03 ` Nathan Lynch
2015-08-08 2:03 ` [PATCH 1/2] ARM: VDSO: fix coarse clock monotonicity regression Nathan Lynch
2015-08-08 2:03 ` Nathan Lynch
2015-08-10 9:08 ` Will Deacon
2015-08-10 9:08 ` Will Deacon
2015-08-08 2:03 ` [PATCH 2/2] arm64: " Nathan Lynch
2015-08-08 2:03 ` Nathan Lynch
2015-08-10 9:22 ` Will Deacon
2015-08-10 9:22 ` Will Deacon
2015-08-10 14:58 ` Catalin Marinas
2015-08-10 14:58 ` Catalin Marinas
2015-08-12 20:00 ` John Stultz
2015-08-12 20:00 ` John Stultz
2015-08-10 15:46 ` [PATCH v2] ARM: " Nathan Lynch
2015-08-10 15:46 ` Nathan Lynch
2015-08-10 15:48 ` Will Deacon [this message]
2015-08-10 15:48 ` Will Deacon
2015-08-12 20:00 ` John Stultz
2015-08-12 20:00 ` John Stultz
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=20150810154815.GH1604@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.