Ingo Molnar <mingo@elte.hu> wrote:
>
> But on 2.6 the timer will run precisely on the CPU it was added, so i
> think the race is not possible.
well there is add_timer_on()...
I still don't see the race in the itimer code actually. On return
from del_timer_sync() we know that the timer is not pending, even
if it_real_fn() tried to re-add it.
ie: why does the below "crash"?
Andrea Arcangeli <andrea@suse.de> wrote:
>
> cpu0 cpu1
> ------------ --------------------
>
> do_setitimer
> it_real_fn
> del_timer_sync add_timer -> crash
(Does the timer_pending() test in del_timer_sync() needs some
barriers btw?)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:44 EST