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
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
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 -
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 -
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]
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]
6 matches
Mail list logo