Re: [RT PATCH 2/3] hrtimer: Don't grab the expiry lock for non-soft hrtimer

2019-08-21 Thread Sebastian Andrzej Siewior
On 2019-08-21 10:24:08 [+0100], Julien Grall wrote: > diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c > index b869e816e96a..119414a2f59c 100644 > --- a/kernel/time/hrtimer.c > +++ b/kernel/time/hrtimer.c > @@ -934,7 +934,7 @@ void hrtimer_grab_expiry_lock(const struct hrtimer *timer) >

[RT PATCH 2/3] hrtimer: Don't grab the expiry lock for non-soft hrtimer

2019-08-21 Thread Julien Grall
There are no guarantee the hrtimer_cancel() will be called on the same CPU as the non-soft hrtimer is running on so the following scenario can happen. CPU0 | CPU1 | |