Re: [PATCH 0/2][RFC] Potential fix for leapsecond caused futex issue
(v2)
[Posted July 2, 2012 by corbet]
| From: |
| John Stultz <johnstul-AT-us.ibm.com> |
| To: |
| Linux Kernel <linux-kernel-AT-vger.kernel.org> |
| Subject: |
| Re: [PATCH 0/2][RFC] Potential fix for leapsecond caused futex issue
(v2) |
| Date: |
| Sun, 01 Jul 2012 21:12:59 -0700 |
| Message-ID: |
| <4FF11FCB.4030207@us.ibm.com> |
| Cc: |
| Prarit Bhargava <prarit-AT-redhat.com>, stable-AT-vger.kernel.org,
Thomas Gleixner <tglx-AT-linutronix.de> |
| Archive-link: |
| Article, Thread
|
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
kernel.org.
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:
http://git.linaro.org/gitweb?p=people/jstultz/linux.git;a...
I did boot and test each of those kernels with my leaptest-timer.c test
successfully.
thanks
-john
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
(
Log in to post comments)