From: Shivank Garg <shivankg@amd.com>
To: Luiz Capitulino <luizcap@redhat.com>,
david@redhat.com, willy@infradead.org, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, sj@kernel.org,
harry.yoo@oracle.com
Subject: Re: [PATCH v3 0/4] mm: introduce snapshot_page()
Date: Mon, 14 Jul 2025 19:25:32 +0530 [thread overview]
Message-ID: <226304ff-e8f3-4ba0-812c-f1356d4d8de1@amd.com> (raw)
In-Reply-To: <cover.1752499009.git.luizcap@redhat.com>
On 7/14/2025 6:46 PM, Luiz Capitulino wrote:
> Hi,
>
> The series introduction will follow the changelog. This is against bc9ff192a6c9 .
>
> Changelog
> =========
>
> v2 -> v3
> - Small snapshot_page() refactor to simplify and fix stack-out-of-bugs bug
> reported by Harry Yoo
> - Use clear_compound_head() in snapshot_page() (Shivank)
> - Read head pointer from ps->page_snapshot() for tail page case (Shivank)
> - Improve comments and macro name in snapshot_page() (David)
>
> v1 -> v2
> - Include is_huge_zero_pfn() patch and use it (David)
> - Move free page detection to snapshot_page() (David)
> - Changelog improvements (Shivank)
> - Added Acked-bys
>
> RFC -> v1
> - Include <linux/page_idle.h> to avoid build error on sh arch
>
> Introduction
> ============
>
> This series introduces snapshot_page(), a helper function that can be used
> to create a snapshot of a struct page and its associated struct folio.
>
> This function is intended to help callers with a consistent view of a
> a folio while reducing the chance of encountering partially updated or
> inconsistent state, such as during folio splitting which could lead to
> crashes and BUG_ON()s being triggered.
>
> David Hildenbrand (1):
> mm/memory: introduce is_huge_zero_pfn() and use it in
> vm_normal_page_pmd()
>
> Luiz Capitulino (3):
> mm/util: introduce snapshot_page()
> proc: kpagecount: use snapshot_page()
> fs: stable_page_flags(): use snapshot_page()
>
> fs/proc/page.c | 50 +++++++++++++++-----------
> include/linux/huge_mm.h | 12 ++++++-
> include/linux/mm.h | 19 ++++++++++
> mm/debug.c | 42 +++-------------------
> mm/memory.c | 2 +-
> mm/util.c | 79 +++++++++++++++++++++++++++++++++++++++++
> 6 files changed, 144 insertions(+), 60 deletions(-)
>
The changes look good to me.
Thanks for addressing the feedback.
Reviewed-by: Shivank Garg <shivankg@amd.com>
next prev parent reply other threads:[~2025-07-14 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 13:16 [PATCH v3 0/4] mm: introduce snapshot_page() Luiz Capitulino
2025-07-14 13:16 ` [PATCH v3 1/4] mm/memory: introduce is_huge_zero_pfn() and use it in vm_normal_page_pmd() Luiz Capitulino
2025-07-14 14:26 ` David Hildenbrand
2025-07-14 13:16 ` [PATCH v3 2/4] mm/util: introduce snapshot_page() Luiz Capitulino
2025-07-16 10:16 ` David Hildenbrand
2025-07-16 17:36 ` Luiz Capitulino
2025-07-16 18:18 ` David Hildenbrand
2025-07-16 22:19 ` Andrew Morton
2025-07-17 1:52 ` Luiz Capitulino
2025-07-17 15:54 ` Luiz Capitulino
2025-07-14 13:16 ` [PATCH v3 3/4] proc: kpagecount: use snapshot_page() Luiz Capitulino
2025-07-16 10:17 ` David Hildenbrand
2025-07-16 17:41 ` Luiz Capitulino
2025-07-16 18:18 ` David Hildenbrand
2025-07-14 13:16 ` [PATCH v3 4/4] fs: stable_page_flags(): " Luiz Capitulino
2025-07-16 10:19 ` David Hildenbrand
2025-07-14 13:55 ` Shivank Garg [this message]
2025-07-15 22:53 ` [PATCH v3 0/4] mm: introduce snapshot_page() Harry Yoo
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=226304ff-e8f3-4ba0-812c-f1356d4d8de1@amd.com \
--to=shivankg@amd.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luizcap@redhat.com \
--cc=sj@kernel.org \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).