[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yofu5wUgov+2eVCE@qian>
Date: Fri, 20 May 2022 15:41:27 -0400
From: Qian Cai <quic_qiancai@...cinc.com>
To: Zi Yan <ziy@...dia.com>
CC: David Hildenbrand <david@...hat.com>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>,
<virtualization@...ts.linux-foundation.org>,
Vlastimil Babka <vbabka@...e.cz>,
Mel Gorman <mgorman@...hsingularity.net>,
Eric Ren <renzhengeek@...il.com>,
Mike Rapoport <rppt@...nel.org>,
"Oscar Salvador" <osalvador@...e.de>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v11 0/6] Use pageblock_order for cma and
alloc_contig_range alignment.
On Fri, May 20, 2022 at 10:13:51AM -0400, Zi Yan wrote:
> Also, do you mind providing the page dump of the 512-page compound page? I would like
> to know what page caused the issue.
page last allocated via order 9, migratetype Movable, gfp_mask 0x3c24ca(GFP_TRANSHUGE|__GFP_THISNODE), pid 831, tgid 831 (khugepaged), ts 3899865924520, free_ts 3821953009040
post_alloc_hook
get_page_from_freelist
__alloc_pages
khugepaged_alloc_page
collapse_huge_page
khugepaged_scan_pmd
khugepaged_scan_mm_slot
khugepaged
kthread
ret_from_fork
page last free stack trace:
free_pcp_prepare
free_unref_page
free_compound_page
free_transhuge_page
__put_compound_page
release_pages
free_pages_and_swap_cache
tlb_batch_pages_flush
tlb_finish_mmu
exit_mmap
__mmput
mmput
exit_mm
do_exit
do_group_exit
__arm64_sys_exit_group
Powered by blists - more mailing lists