Re: [PATCH v2] slub: use jitter-free reference while printing age

2018-03-08 Thread Chintan Pandya
On 3/8/2018 11:42 PM, Christopher Lameter wrote: On Thu, 8 Mar 2018, Chintan Pandya wrote: In this case, object got freed later but 'age' shows otherwise. This could be because, while printing this info, we print allocation traces first and free traces thereafter. In between, if we get

Re: [PATCH v2] slub: use jitter-free reference while printing age

2018-03-08 Thread Chintan Pandya
On 3/8/2018 11:42 PM, Christopher Lameter wrote: On Thu, 8 Mar 2018, Chintan Pandya wrote: In this case, object got freed later but 'age' shows otherwise. This could be because, while printing this info, we print allocation traces first and free traces thereafter. In between, if we get

Re: [PATCH v2] slub: use jitter-free reference while printing age

2018-03-08 Thread Christopher Lameter
On Thu, 8 Mar 2018, Chintan Pandya wrote: > In this case, object got freed later but 'age' > shows otherwise. This could be because, while > printing this info, we print allocation traces > first and free traces thereafter. In between, > if we get schedule out or jiffies increment, > (jiffies -

Re: [PATCH v2] slub: use jitter-free reference while printing age

2018-03-08 Thread Christopher Lameter
On Thu, 8 Mar 2018, Chintan Pandya wrote: > In this case, object got freed later but 'age' > shows otherwise. This could be because, while > printing this info, we print allocation traces > first and free traces thereafter. In between, > if we get schedule out or jiffies increment, > (jiffies -

[PATCH v2] slub: use jitter-free reference while printing age

2018-03-07 Thread Chintan Pandya
When SLUB_DEBUG catches the some issues, it prints all the required debug info. However, in few cases where allocation and free of the object has have happened in a very short time, 'age' might mislead. See the example below, [ 6044.137581]

[PATCH v2] slub: use jitter-free reference while printing age

2018-03-07 Thread Chintan Pandya
When SLUB_DEBUG catches the some issues, it prints all the required debug info. However, in few cases where allocation and free of the object has have happened in a very short time, 'age' might mislead. See the example below, [ 6044.137581]