On 01/31/2014 05:37 AM, Luis Henriques wrote:
> On Thu, Jan 30, 2014 at 09:58:21AM -0800, John Stultz wrote:
>>
>> Yes, and I have already tested (x86,i386,arm) backports ready for 3.13,
>> 3.10 and 3.4 here:
>>
>> git://git.linaro.org/people/john.stultz/linux.git stable/3.13/timefix
>> git://git.linaro.org/people/john.stultz/linux.git stable/3.10/timefix
>> git://git.linaro.org/people/john.stultz/linux.git stable/3.4/timefix
>>
>> (Note: The 3.4 tree also has an additional fix thats been hanging out in
>> the AOSP tree for months).
>>
>> But since these landed in the 3.14 merge window, I'll be waiting till
>> after -rc2 to submit them.
>>
>> For 2.6.34 and 2.6.32, the clock_was_set_delayed() call raises a softirq
>> instead of calling sched_work, so it shouldn't have the deadlock issue
>> fixed in the series above.
> Great, thanks a lot for the clarification (and the backports!). I'll
> queue these for the 3.5 and 3.11 kernels once -rc1 is out.
Oh... I didn't realize 3.5 and 3.11 were still being maintained
(kernel.org doesn't list them).
The 3.4 tree will probably port to 3.5 relatively cleanly... And the
3.13 set would probably more easily port to 3.11 then the 3.10 set. Let
me know if you run into trouble there.
As for something to validate with, I've got my test collection here:
https://github.com/johnstultz-work/timetests
And again, feel free to queue them, but don't apply until after rc2
(I'll be resubmitting my queues then).
thanks
-john
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html