Re: [PATCH] timers: Fix overflow in get_next_timer_interrupt

2017-08-01 Thread Alexander Sverdlin
On 01/08/17 09:11, Matija Glavinic Pecotic wrote: > For e.g. HZ=100, timer being 430 jiffies in the future, and 32 bit > unsigned int, there is an overflow on unsigned int right-hand side > of the expression which results with wrong values being returned. > > Problem was observed on tickless core

Re: [PATCH] timers: Fix overflow in get_next_timer_interrupt

2017-08-01 Thread Alexander Sverdlin
On 01/08/17 09:11, Matija Glavinic Pecotic wrote: > For e.g. HZ=100, timer being 430 jiffies in the future, and 32 bit > unsigned int, there is an overflow on unsigned int right-hand side > of the expression which results with wrong values being returned. > > Problem was observed on tickless core

[PATCH] timers: Fix overflow in get_next_timer_interrupt

2017-08-01 Thread Matija Glavinic Pecotic
For e.g. HZ=100, timer being 430 jiffies in the future, and 32 bit unsigned int, there is an overflow on unsigned int right-hand side of the expression which results with wrong values being returned. Problem was observed on tickless core and with following applied: sched/nohz: add

[PATCH] timers: Fix overflow in get_next_timer_interrupt

2017-08-01 Thread Matija Glavinic Pecotic
For e.g. HZ=100, timer being 430 jiffies in the future, and 32 bit unsigned int, there is an overflow on unsigned int right-hand side of the expression which results with wrong values being returned. Problem was observed on tickless core and with following applied: sched/nohz: add