Re: Query:Regarding percpu_counter debug object destroy

2018-04-13 Thread Kohli, Gaurav
Hi Nikolay, Thanks for the comment. I agree ,like timer , hrtimer we have to mark inactive in destroy function and finally freeing the debug object after destruction of percpu_counter. But i am still not sure that this double freeing with same address may create race or not in debug_object l

Re: Query:Regarding percpu_counter debug object destroy

2018-04-13 Thread Nikolay Borisov
On 13.04.2018 10:32, Kohli, Gaurav wrote: > Hi , > > I have checked below code and it seems we are calling debug_object_free > twice, ideally we should deactivate and later we > have to destroy. > > 1st call -> percpu_counter_destroy->debug_percpu_counter_deactivate -> > debug_object_free > 2nd

Query:Regarding percpu_counter debug object destroy

2018-04-13 Thread Kohli, Gaurav
Hi , I have checked below code and it seems we are calling debug_object_free twice, ideally we should deactivate and later we have to destroy. 1st call -> percpu_counter_destroy->debug_percpu_counter_deactivate -> debug_object_free 2nd call -> debug_object_free static bool percpu_counter_fi