On Tue, Sep 11, 2012 at 06:35:23PM -0400, John Stultz wrote:I did send them out for 3.0, on Sep 11.Just wanted to send out a few timekeeping fixes that were mergedDid you also send these out for the 3.0.y tree and I just missed them?
in 3.6 which are appropriate for -stable.
This queue backports the following fixes:
-----------------------------------------
cee58483cf56e0ba355fdd97ff5e8925329aa936 time: Move ktime_t overflow checking into timespec_valid_strict
bf2ac312195155511a0f79325515cbb61929898a time: Avoid making adjustments if we haven't accumulated anything
4e8b14526ca7fb046a81c94002c1c43b6fdf0e9b time: Improve sanity checking of timekeeping inputs
I've run these through my timetest suite w/ kvm on both i386
& x86_64. But more testing would be of course appreciated.
https://github.com/johnstultz-work/timetests
I also have patch queues for all the -stable trees that I'll be
sending out as my testing completes for those trees.
Should I just take this 3.2.y series and see how they well apply?