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 <[email protected]> > Cc: John Stultz <[email protected]> > Cc: Thomas Gleixner <[email protected]> > Cc: Miroslav Lichvar <[email protected]>
John, ACK? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
