| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20150210140155.GA7119@twins.programming.kicks-ass.net> Date: Tue, 10 Feb 2015 15:01:55 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Prarit Bhargava <prarit@...hat.com> Cc: linux-kernel@...r.kernel.org, John Stultz <john.stultz@...aro.org>, Thomas Gleixner <tglx@...utronix.de>, Miroslav Lichvar <mlichvar@...hat.com> Subject: Re: [PATCH] time, ntp: Do not update time_state in middle of leap second On Sat, Feb 07, 2015 at 01:29:39PM -0500, Prarit Bhargava wrote: > During leap second insertion testing it was noticed that a small window > exists where the time_state could be reset such that > time_state = TIME_OK, which then causes the leap second to not occur, or > causes the entire leap second state machine to fail. > > While this is highly unlikely to ever happen in the real world it is > still something we should protect against, as breaking the state machine > is obviously bad. > > If the time_state == TIME_OOP (ie, the leap second is in progress) do not > allow an external update to time_state. > > [v2]: Only block time_state change when TIME_OOP > > Signed-off-by: Prarit Bhargava <prarit@...hat.com> > Cc: John Stultz <john.stultz@...aro.org> > Cc: Thomas Gleixner <tglx@...utronix.de> > Cc: Miroslav Lichvar <mlichvar@...hat.com> John, ACK? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists