From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Pedro Demarchi Gomes <pedrodemargomes@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Xu Xin <xu.xin16@zte.com.cn>,
Chengming Zhou <chengming.zhou@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] Revert "mm/ksm: convert break_ksm() from walk_page_range_vma() to folio_walk"
Date: Wed, 5 Nov 2025 15:21:18 +0100 [thread overview]
Message-ID: <c6e5aa34-25ab-44f9-b6dc-127f3084adc8@kernel.org> (raw)
In-Reply-To: <42byvvz55omaszu6ep3g7n2dj5z7mfxy5h3zbc3xjdnslemkpp@kvdzrjz423mb>
On 05.11.25 14:28, Pedro Demarchi Gomes wrote:
> On Mon, Nov 03, 2025 at 06:00:08PM +0100, David Hildenbrand (Red Hat) wrote:
>> On 31.10.25 18:46, Pedro Demarchi Gomes wrote:
>>> This reverts commit e317a8d8b4f600fc7ec9725e26417030ee594f52 and changes
>>> function break_ksm_pmd_entry() to use folios.
>>>
>>> This reverts break_ksm() to use walk_page_range_vma() instead of
>>> folio_walk_start().
>>> This will make it easier to later modify break_ksm() to perform a proper
>>> range walk.
>>>
>>> Suggested-by: David Hildenbrand <david@redhat.com>
>>> Signed-off-by: Pedro Demarchi Gomes <pedrodemargomes@gmail.com>
>>> ---
>>> mm/ksm.c | 63 ++++++++++++++++++++++++++++++++++++++++++--------------
>>> 1 file changed, 47 insertions(+), 16 deletions(-)
>>>
>>> diff --git a/mm/ksm.c b/mm/ksm.c
>>> index 4f672f4f2140..922d2936e206 100644
>>> --- a/mm/ksm.c
>>> +++ b/mm/ksm.c
>>> @@ -607,6 +607,47 @@ static inline bool ksm_test_exit(struct mm_struct *mm)
>>> return atomic_read(&mm->mm_users) == 0;
>>> }
>>> +static int break_ksm_pmd_entry(pmd_t *pmd, unsigned long addr, unsigned long next,
>>> + struct mm_walk *walk)
>>> +{
>>> + struct folio *folio = NULL;
>>> + spinlock_t *ptl;
>>> + pte_t *pte;
>>> + pte_t ptent;
>>> + int ret;
>>> +
>>> + pte = pte_offset_map_lock(walk->mm, pmd, addr, &ptl);
>>> + if (!pte)
>>> + return 0;
>>> + ptent = ptep_get(pte);
>>> + if (pte_present(ptent)) {
>>> + folio = vm_normal_folio(walk->vma, addr, ptent);
>>> + } else if (!pte_none(ptent)) {
>>> + swp_entry_t entry = pte_to_swp_entry(ptent);
>>> +
>>> + /*
>>> + * As KSM pages remain KSM pages until freed, no need to wait
>>> + * here for migration to end.
>>> + */
>>> + if (is_migration_entry(entry))
>>> + folio = pfn_swap_entry_folio(entry);
>>> + }
>>> + /* return 1 if the page is an normal ksm page or KSM-placed zero page */
>>> + ret = (folio && folio_test_ksm(folio)) || is_ksm_zero_pte(ptent);
>>
>> Staring again, we should really call is_ksm_zero_pte() only if we know the
>> folio is present.
>>
>> It's not super dangerous in the old code (because we would only look at
>> present an migration entries), but now you are making it possible to call it
>> on even more non-present ptes.
>>
>
> IIUC vm_normal_folio will return NULL in the case of a ksm zero pte, so
> we can not do
> found = folio && (folio_test_ksm(folio) || is_ksm_zero_pte(pte))
> because it will always be false for a ksm zero pte.
> So we should do
> found = (folio && folio_test_ksm(folio)) || (pte_present(ptent)
> && is_ksm_zero_pte(ptent));
> since if the pte is present and is a zero pte we can guarantee that
> the folio is present.
Yes exactly.
--
Cheers
David
next prev parent reply other threads:[~2025-11-05 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 17:46 [PATCH v2 0/3] ksm: perform a range-walk to jump over holes in break_ksm Pedro Demarchi Gomes
2025-10-31 17:46 ` [PATCH v2 1/3] Revert "mm/ksm: convert break_ksm() from walk_page_range_vma() to folio_walk" Pedro Demarchi Gomes
2025-11-03 17:00 ` David Hildenbrand (Red Hat)
2025-11-05 13:28 ` Pedro Demarchi Gomes
2025-11-05 14:21 ` David Hildenbrand (Red Hat) [this message]
2025-10-31 17:46 ` [PATCH v2 2/3] ksm: perform a range-walk in break_ksm Pedro Demarchi Gomes
2025-11-03 17:06 ` David Hildenbrand (Red Hat)
2025-11-05 13:32 ` Pedro Demarchi Gomes
2025-10-31 17:46 ` [PATCH v2 3/3] ksm: replace function unmerge_ksm_pages with break_ksm Pedro Demarchi Gomes
2025-11-03 17:06 ` David Hildenbrand (Red Hat)
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=c6e5aa34-25ab-44f9-b6dc-127f3084adc8@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pedrodemargomes@gmail.com \
--cc=xu.xin16@zte.com.cn \
/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).