Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Liu <ye.liu@linux.dev>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	Brendan Jackman <jackmanb@google.com>,
	Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 9/9] mm/page_owner: use memcg_data snapshot to avoid TOCTOU in print_page_owner_memcg()
Date: Mon, 20 Jul 2026 10:45:56 +0800	[thread overview]
Message-ID: <e3f17e17-495e-423c-9c21-48aace4367d1@linux.dev> (raw)
In-Reply-To: <21007313-40dc-46fb-bbf2-453c8eedf3e8@kernel.org>



在 2026/7/14 16:24, Vlastimil Babka (SUSE) 写道:
> On 7/14/26 03:51, Ye Liu wrote:
>> print_page_owner_memcg() takes a snapshot of page->memcg_data via
>> READ_ONCE at the top of the function and guards against tail pages and
>> NULL memcg_data.  However, it later calls two functions that re-read
>> page->memcg_data locklessly:
>>
>>   1) page_memcg_check(page) — re-reads page->memcg_data;
>>   2) PageMemcgKmem(page) — calls folio_memcg_kmem(), which re-reads
>>      folio->memcg_data and folio->page->compound_head, wrapping both
>>      in VM_BUG_ON assertions:
>>
>>         VM_BUG_ON_PGFLAGS(PageTail(&folio->page), &folio->page);
>>         VM_BUG_ON_FOLIO(folio->memcg_data & MEMCG_DATA_OBJEXTS, folio);
>>
>> If the page is concurrently freed and reallocated as a THP tail page
>> or a slab page between the initial guards and these later calls, the
>> VM_BUG_ON assertions can fire on debug builds (CONFIG_DEBUG_VM=y),
>> causing a kernel panic.
>>
>> Fix both TOCTOU issues by using the memcg_data snapshot throughout:
>>   - Extract objcg from the snapshot via objcg = (void *)(memcg_data &
>>     ~OBJEXTS_FLAGS_MASK) instead of calling page_memcg_check(page);
>>   - Test (memcg_data & MEMCG_DATA_KMEM) instead of calling
>>     PageMemcgKmem(page), which is semantically equivalent:
>>     PageMemcgKmem()->folio_memcg_kmem()->folio->memcg_data &
>>     MEMCG_DATA_KMEM.
>>   - When memcg_data has MEMCG_DATA_OBJEXTS set, early-return after
>>     printing "Slab cache page\n" since objcg != memcg for slab pages
>>     and there is no meaningful cgroup to look up.
> 
> These points have too much detail that's already in the code. Would just
> mention that we opencode applicable parts of page_memcg_check() and
> PageMemcgKmem() using the snapshot?
Yes,It's a bit wordy.
> 
>> This avoids both TOCTOU windows and the assertions entirely.
>>
>> Signed-off-by: Ye Liu <ye.liu@linux.dev>
> 
> Reviewed-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
> 
> Was all of this reported by sashiko? At least the new-in-v6 was?
> Then:
> 
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> 
> But it's no longer a cleanup but a fix, so probably this?
> 
> Fixes: fcf8935832b8 ("mm/page_owner: print memcg information")
> Cc: stable@vger.kernel.org
> 
> It's not fixing a new regression so I think it's fine to keep it part of
> this series for next release and not need to split out for mm-hotfixes.
> 
Hi Andrew,

Could you please help me revise the above? Should I send you V7?


>> ---
>> Changes in v6:
>> - Rename patch to cover both TOCTOU fixes rather than only
>>   PageMemcgKmem().
>> - Also replace page_memcg_check(page) with extracting objcg from the
>>   memcg_data snapshot to fix a second TOCTOU issue.
>> - Add early return for the MEMCG_DATA_OBJEXTS (slab) case since
>>   objcg != memcg for slab pages and there is no cgroup to look up.
>> - Update commit message to cover all changes.
>> - Link: https://lore.kernel.org/all/20260701061101.344679-10-ye.liu@linux.dev/
>>  mm/page_owner.c | 10 +++++++---
>>  1 file changed, 7 insertions(+), 3 deletions(-)
>>
>> diff --git a/mm/page_owner.c b/mm/page_owner.c
>> index 2e3880053a34..e18512a49e38 100644
>> --- a/mm/page_owner.c
>> +++ b/mm/page_owner.c
>> @@ -540,6 +540,7 @@ static inline int print_page_owner_memcg(char *kbuf, size_t count, int ret,
>>  					 struct page *page)
>>  {
>>  	unsigned long memcg_data;
>> +	struct obj_cgroup *objcg;
>>  	struct mem_cgroup *memcg;
>>  	bool online;
>>  	char name[80];
>> @@ -549,11 +550,14 @@ static inline int print_page_owner_memcg(char *kbuf, size_t count, int ret,
>>  	if (!memcg_data || PageTail(page))
>>  		goto out_unlock;
>>  
>> -	if (memcg_data & MEMCG_DATA_OBJEXTS)
>> +	if (memcg_data & MEMCG_DATA_OBJEXTS) {
>>  		ret += scnprintf(kbuf + ret, count - ret,
>>  				"Slab cache page\n");
>> +		goto out_unlock;
>> +	}
>>  
>> -	memcg = page_memcg_check(page);
>> +	objcg = (void *)(memcg_data & ~OBJEXTS_FLAGS_MASK);
>> +	memcg = objcg ? obj_cgroup_memcg(objcg) : NULL;
>>  	if (!memcg)
>>  		goto out_unlock;
>>  
>> @@ -561,7 +565,7 @@ static inline int print_page_owner_memcg(char *kbuf, size_t count, int ret,
>>  	cgroup_name(memcg->css.cgroup, name, sizeof(name));
>>  	ret += scnprintf(kbuf + ret, count - ret,
>>  			"Charged %sto %smemcg %s\n",
>> -			PageMemcgKmem(page) ? "(via objcg) " : "",
>> +			(memcg_data & MEMCG_DATA_KMEM) ? "(via objcg) " : "",
>>  			online ? "" : "offline ",
>>  			name);
>>  out_unlock:
> 

-- 
Thanks,
Ye Liu



  reply	other threads:[~2026-07-20  2:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  1:50 [PATCH v6 0/9] mm/page_owner: misc cleanups Ye Liu
2026-07-14  1:51 ` [PATCH v6 1/9] mm/page_owner: extract skip_buddy_pages() helper to unify buddy page skipping Ye Liu
2026-07-14  1:51 ` [PATCH v6 2/9] mm/page_owner: add MR_NEVER to enum migrate_reason and use it for last_migrate_reason Ye Liu
2026-07-14 13:05   ` David Hildenbrand (Arm)
2026-07-14 13:09     ` Vlastimil Babka (SUSE)
2026-07-14 13:22       ` David Hildenbrand (Arm)
2026-07-14 13:49         ` Vlastimil Babka (SUSE)
2026-07-14 14:44           ` David Hildenbrand (Arm)
2026-07-20  2:39             ` Ye Liu
2026-07-14  1:51 ` [PATCH v6 3/9] mm: use enum migrate_reason instead of int for migration reason parameters Ye Liu
2026-07-14 13:07   ` David Hildenbrand (Arm)
2026-07-14  1:51 ` [PATCH v6 4/9] mm/page_owner: hoist CONFIG_MEMCG to function level for print_page_owner_memcg() Ye Liu
2026-07-14  1:51 ` [PATCH v6 5/9] mm/page_owner: add missing newline to count_threshold format string Ye Liu
2026-07-14  1:51 ` [PATCH v6 6/9] mm/page_owner: move free_ts_nsec output to free section in __dump_page_owner() Ye Liu
2026-07-14  1:51 ` [PATCH v6 7/9] mm/page_owner: drop redundant page_owner prefix from static symbols Ye Liu
2026-07-14  1:51 ` [PATCH v6 8/9] mm/page_owner: clamp skip_buddy_pages() PFN advance at MAX_ORDER_NR_PAGES boundary Ye Liu
2026-07-14  1:51 ` [PATCH v6 9/9] mm/page_owner: use memcg_data snapshot to avoid TOCTOU in print_page_owner_memcg() Ye Liu
2026-07-14  1:56   ` Zi Yan
2026-07-14  8:24   ` Vlastimil Babka (SUSE)
2026-07-20  2:45     ` Ye Liu [this message]
2026-07-20  5:42       ` Andrew Morton
2026-07-20  6:58         ` Ye Liu
2026-07-14  3:16 ` [PATCH v6 0/9] mm/page_owner: misc cleanups Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e3f17e17-495e-423c-9c21-48aace4367d1@linux.dev \
    --to=ye.liu@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=jackmanb@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=ziy@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox