hrtimer: HRTIMER_STATE_ fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | hrtimer: kill HRTIMER_STATE_MIGRATE, fix the race with hrtimer_is_queued()include/ kernel/ | +3 | 1 reply | |
| 1/3 | hrtimer: kill HRTIMER_STATE_MIGRATE, fix the race with hrtimer_is_queued()include/ kernel/ | +3 | 0 replies | |
| 2/3 | hrtimer: turn newstate arg of __remove_hrtimer() into clear_enqueuedkernel/ | +9 | 0 replies | |
| 3/3 | hrtimer: fix the __hrtimer_start_range_ns() race with hrtimer_active()kernel/ | +5 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] hrtimer: HRTIMER_STATE_ fixes
Quoted 6 lines · Peter Zijlstra
Quoted 3 lines
I tend to agree, but I think its a pre-existing problem, not one introduced by my proposed patch.
Something like this would fix that I think. It fully preserves
timer->stateoverhrtimer_start_range_ns().
Yes, but I think we can do a bit better.
Only for initial review, I need to re-check this...
And. I think that after you remove STATE_CALLBACK we can even kill timer->state altogether, but this is another story.
What do you think?
Oleg.