[lkml]   [2012]   [Jul]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/2][RFC] Potential fix for leapsecond caused futex issue (v2)
On 07/01/2012 11:29 AM, John Stultz wrote:
> TODOs:
> * Chase down the futex/hrtimer interaction to see if this could
> be triggered in any other way.
> * Get Tglx's input/ack
> * Generate a backport for pre-v3.4 kernels
So while still waiting for feedback on the clock_was_set() change, I
went ahead and generated backports for most of the stable kernels on

Clearly these shouldn't go anywhere until the fix is upstream, but since
I assume there's a number of distro developers who are likely under
pressure to have a fix soon, I wanted to make them available so no one
is duplicating work.

You can find them here:;a=summary

I did boot and test each of those kernels with my leaptest-timer.c test


 \ /
  Last update: 2012-07-02 06:43    [W:0.086 / U:1.432 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site