Ben Hutchings wrote:

On Fri, 2012-06-15 at 11:56 -0700, John Stultz wrote:

quoted

commit dd48d708ff3e917f6d6b6c2b696c3f18c019feed upstream.

[...]

This doesn't apply to 3.2.y, unsurprisingly.  Let me know if there are
any urgent leap second fixes that will be needed there.

6b43ae8a619d (ntp: Fix leap-second hrtimer livelock) sounds important,
but the patch depends on bd3312681f69 (ntp: Add ntp_lock to replace
xtime_locking) which does not have a commit message explaining its
purpose (and that patch in turn depends on ea7cf49a7633).

John, is that bug present in 3.2.y and 3.0.y, too?  Any hints for
fixing it?

Thanks,
Jonathan