In looking into the lockdep splat reported by Sasha this week, and came across a number of issues in the timekeeping code (some related and some not).
Since I sent out v1, I came across another problem, as well as a fix for the lockdep issue, so I wanted to resend the patches for comment. My current thought is that the first three patches are probably urgent 3.13 items, where as the last two can probably be deferred to 3.14. The TAI timer delay thinko is particularly embarrassing, but sine CLOCK_TAI was introduced in 3.10, its not exactly a regression, and probably doesn't yet have any users outside of my tests. Ingo/Thomas: Let me know if you agree with the first three patches as urgent. I'd probably skip the second, but it provides the infrastructure for the lockdep solution. Sigh. Back-porting that lockdep fix to 3.10 will be a bit of a pain, and I'll have to look to see if we need it even further back or not. thanks -john Cc: Thomas Gleixner <[email protected]> Cc: Prarit Bhargava <[email protected]> Cc: Richard Cochran <[email protected]> Cc: Ingo Molnar <[email protected]> John Stultz (5): timekeeping: Fix lost updates to tai adjustment timekeeping: Fix potential lost pv notification of time change timekeeping: Avoid possible deadlock from clock_was_set_delayed timekeeping: Fix CLOCK_TAI timer/nanosleep delays timekeeping: Fix missing timekeeping_update in suspend path kernel/time/timekeeping.c | 37 +++++++++++++++++++++++++++---------- 1 file changed, 27 insertions(+), 10 deletions(-) -- 1.8.3.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
