public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Stefan Liebler <stli@linux.vnet.ibm.com>,
	Preeti U Murthy <preeti@linux.vnet.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: futex timeout not working? (bisected)
Date: Fri, 16 Oct 2015 15:41:25 +0200	[thread overview]
Message-ID: <20151016134125.GE6354@osiris> (raw)
In-Reply-To: <alpine.DEB.2.11.1510161443520.4212@nanos>

On Fri, Oct 16, 2015 at 02:45:37PM +0200, Thomas Gleixner wrote:
> The only point I found which does not update the sequence count is
> timekeeping_init().
> 
> Does the patch below fix your issue?
> 

Yes, it does. Thanks for looking into this and fixing it!


> 8<--------------------
> 
> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
> index 3739ac6aa473..44d2cc0436f4 100644
> --- a/kernel/time/timekeeping.c
> +++ b/kernel/time/timekeeping.c
> @@ -1251,7 +1251,7 @@ void __init timekeeping_init(void)
>  	set_normalized_timespec64(&tmp, -boot.tv_sec, -boot.tv_nsec);
>  	tk_set_wall_to_mono(tk, tmp);
> 
> -	timekeeping_update(tk, TK_MIRROR);
> +	timekeeping_update(tk, TK_MIRROR | TK_CLOCK_WAS_SET);
> 
>  	write_seqcount_end(&tk_core.seq);
>  	raw_spin_unlock_irqrestore(&timekeeper_lock, flags);
> 


      reply	other threads:[~2015-10-16 13:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 10:43 futex timeout not working? (bisected) Heiko Carstens
2015-10-16 10:21 ` Thomas Gleixner
2015-10-16 10:31   ` Heiko Carstens
2015-10-16 10:33     ` Thomas Gleixner
2015-10-16 10:38       ` Heiko Carstens
2015-10-16 10:35     ` Thomas Gleixner
2015-10-16 10:54       ` Heiko Carstens
2015-10-16 11:50         ` Heiko Carstens
2015-10-16 12:19           ` Thomas Gleixner
2015-10-16 12:45             ` Thomas Gleixner
2015-10-16 13:41               ` Heiko Carstens [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=20151016134125.GE6354@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=preeti@linux.vnet.ibm.com \
    --cc=stli@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    /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