public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Khlebnikov <khlebnikov@openvz.org>
To: John Stultz <johnstul@us.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Prarit Bhargava <prarit@redhat.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] timekeeping: Add missing update call in timekeeping_resume()
Date: Tue, 17 Jul 2012 12:21:02 +0400	[thread overview]
Message-ID: <5005206E.9040804@openvz.org> (raw)
In-Reply-To: <1342457442-7255-1-git-send-email-johnstul@us.ibm.com>

I run into the same regression in s2ram between v3.5-rc6 and v3.5-rc7.
This patch helps. Thanks.

Tested-by: Konstantin Khlebnikov <khlebnikov@openvz.org>

John Stultz wrote:
> From: Thomas Gleixner<tglx@linutronix.de>
>
> Linus,
> 	Since Thomas is on vacation I wanted to send you his fix to resolve
> the suspend regression from the leapsecond fixes.
>
> thanks
> -john
>
> The leap second rework unearthed another issue of inconsistent data.
>
> On timekeeping_resume() the timekeeper data is updated, but nothing
> calls timekeeping_update(), so now the update code in the timer
> interrupt sees stale values.
>
> This has been the case before those changes, but then the timer
> interrupt was using stale data as well so this went unnoticed for
> quite some time.
>
> Add the missing update call, so all the data is consistent everywhere.
>
> Reported-by: Andreas Schwab<schwab@linux-m68k.org>
> Reported-by-and-tested-by: "Rafael J. Wysocki"<rjw@sisk.pl>
> CC: LKML<linux-kernel@vger.kernel.org>
> Cc: Linux PM list<linux-pm@vger.kernel.org>
> Cc: John Stultz<johnstul@us.ibm.com>
> Cc: Ingo Molnar<mingo@kernel.org>
> Cc: Peter Zijlstra<a.p.zijlstra@chello.nl>,
> Cc: Prarit Bhargava<prarit@redhat.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Thomas Gleixner<tglx@linutronix.de>
> Signed-off-by: John Stultz<johnstul@us.ibm.com>
> ---
>   kernel/time/timekeeping.c |    1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
> index 269b1fe..3447cfa 100644
> --- a/kernel/time/timekeeping.c
> +++ b/kernel/time/timekeeping.c
> @@ -717,6 +717,7 @@ static void timekeeping_resume(void)
>   	timekeeper.clock->cycle_last = timekeeper.clock->read(timekeeper.clock);
>   	timekeeper.ntp_error = 0;
>   	timekeeping_suspended = 0;
> +	timekeeping_update(false);
>   	write_sequnlock_irqrestore(&timekeeper.lock, flags);
>
>   	touch_softlockup_watchdog();


      reply	other threads:[~2012-07-17  8:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 16:50 [PATCH] timekeeping: Add missing update call in timekeeping_resume() John Stultz
2012-07-17  8:21 ` Konstantin Khlebnikov [this message]

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=5005206E.9040804@openvz.org \
    --to=khlebnikov@openvz.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=prarit@redhat.com \
    --cc=stable@vger.kernel.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