Damn, On 06/09, Oleg Nesterov wrote: > > Yes, we only have this 2nd write_seqcount_begin/end if the timer re- > arms itself, but otherwise we do not race. If another thread does > hrtime_start() in between we can pretend that hrtimer_active() hits > the "inactive". ^^^^^^^^^^^^^^^
I meant, hits the "inactive" window we can't avoid. Even if another thread does this _before_ __run_hrtimer() clears ->running, we can't distinguish from the case when it does this right _after_ the timer becomes "inactive". Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/