timekeeping: Increment clock_was_set_seq in timekeeping_init()

timekeeping_init() can set the wall time offset, so we need to
increment the clock_was_set_seq counter. That way hrtimers will pick
up the early offset immediately. Otherwise on a machine which does not
set wall time later in the boot process the hrtimer offset is stale at
0 and wall time timers are going to expire with a delay of 45 years.

Fixes: 868a3e915f7f "hrtimer: Make offset update smarter"
Reported-and-tested-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Stefan Liebler <stli@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: John Stultz <john.stultz@linaro.org>

Changed files
+1 -1
kernel
+1 -1
kernel/time/timekeeping.c
··· 1251 1251 set_normalized_timespec64(&tmp, -boot.tv_sec, -boot.tv_nsec); 1252 1252 tk_set_wall_to_mono(tk, tmp); 1253 1253 1254 - timekeeping_update(tk, TK_MIRROR); 1254 + timekeeping_update(tk, TK_MIRROR | TK_CLOCK_WAS_SET); 1255 1255 1256 1256 write_seqcount_end(&tk_core.seq); 1257 1257 raw_spin_unlock_irqrestore(&timekeeper_lock, flags);