Comment 14 for bug 1020285

Note that even though it's been a while since the leap second, a kernel affected by this bug could persist with its desynced internal idea of time, and the system would show no noticable symptoms until someone eventually runs an effected application. (See https://lkml.org/lkml/2012/7/1/203 and https://lkml.org/lkml/2012/7/10/446 for more details.)

The attatched short Python script can be used to check a particular system to see if the kernel is left in that desynced state (and avoids causing high CPU usage during the test).