On 8/31/2017 1:04 PM, Vlastimil Babka wrote:
On 08/30/2017 09:32 AM, Prakash Gupta wrote:
The page_owner stacktrace always begin as follows:
[] save_stack+0x40/0xc8
[] __set_page_owner+0x3c/0x6c
Hmm, on x86_64 it looks like this:
save_stack_trace+0x16/0x20
save_stack+0x43/0xe0
__set_p
On 08/30/2017 09:32 AM, Prakash Gupta wrote:
> The page_owner stacktrace always begin as follows:
>
> [] save_stack+0x40/0xc8
> [] __set_page_owner+0x3c/0x6c
Hmm, on x86_64 it looks like this:
save_stack_trace+0x16/0x20
save_stack+0x43/0xe0
__set_page_owner+0x24/0x50
So after your patch ther
The page_owner stacktrace always begin as follows:
[] save_stack+0x40/0xc8
[] __set_page_owner+0x3c/0x6c
These two entries do not provide any useful information and limits the
available stacktrace depth. The page_owner stacktrace was skipping caller
function from stack entries but this was misse
3 matches
Mail list logo