mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kunwu Chan <kunwu.chan@gmail.com>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Kunwu Chan <kunwu.chan@linux.dev>,
	Kunwu Chan <kunwu.chan@gmail.com>, Dev Jain <dev.jain@arm.com>,
	akpm@linux-foundation.org, david@kernel.org, riel@surriel.com,
	liam@infradead.org, vbabka@kernel.org, harry@kernel.org,
	jannh@google.com, lance.yang@linux.dev, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/rmap: remove stale hugetlb check in try_to_unmap_one
Date: Tue,  1 Sep 2026 00:41:42 +0800	[thread overview]
Message-ID: <20260831164143.2517715-1-kunwu.chan@linux.dev> (raw)
In-Reply-To: <apWlLTa3oZq1wwvR@lucifer>

On Mon, 31 Aug 2026 17:00:56 +0100 "Lorenzo Stoakes (ARM)" <ljs@kernel.org> wrote:

> On Mon, Aug 31, 2026 at 11:59:12PM +0800, Kunwu Chan wrote:
> > On Mon, 31 Aug 2026 08:28:47 +0000 Dev Jain <dev.jain@arm.com> wrote:
> >
> > > Post commit d4ec5572825a ("mm/rmap: add try_to_unmap_poisoned_hugetlb_one")
> > > try_to_unmap_one() cannot be called with a hugetlb folio. Therefore remove
> > > the folio_test_hugetlb() check.
> >
> > Yes, the d4ec5572825 change shows that try_to_unmap() dispatches
> > hugetlb folios to try_to_unmap_poisoned_hugetlb_one(),
> > so try_to_unmap_one() cannot be called with a hugetlb folio.
> >
> >
> > It would be better to add:
> > Fixes: d4ec5572825 ("mm/rmap: add try_to_unmap_poisoned_hugetlb_one")
> 
> Nope, let's not thanks.
> 
> This isn't a bug.
> 

Got it, thanks for pointing that out. 
I mistakenly treated the stale code as a bug.

Thanks,
KunWu

> >
> > Reviewed-by: Kunwu Chan <kunwu.chan@gmail.com>
> >
> > Thanks,
> > KunWu
> >
> > >
> > > Signed-off-by: Dev Jain <dev.jain@arm.com>
> > > ---
> > > Rebase soup - my huge_ptep_get() fixes landed after the refactoring.
> > >
> > > This patch applies on Linux 7.3-rc1.
> > >
> > >  mm/rmap.c | 7 ++-----
> > >  1 file changed, 2 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/mm/rmap.c b/mm/rmap.c
> > > index d1819fd699380..606c8ecf31302 100644
> > > --- a/mm/rmap.c
> > > +++ b/mm/rmap.c
> > > @@ -2299,11 +2299,8 @@ static bool try_to_unmap_one(struct folio *folio, struct vm_area_struct *vma,
> > >  		VM_BUG_ON_FOLIO(!pvmw.pte, folio);
> > >
> > >  		address = pvmw.address;
> > > -		if (folio_test_hugetlb(folio)) {
> > > -			pteval = huge_ptep_get(mm, address, pvmw.pte);
> > > -		} else {
> > > -			pteval = ptep_get(pvmw.pte);
> > > -		}
> > > +		pteval = ptep_get(pvmw.pte);
> > > +
> > >  		if (likely(pte_present(pteval))) {
> > >  			pfn = pte_pfn(pteval);
> > >  		} else {
> > > --
> > > 2.43.0
> > >
> > >
> >
> 
> --
> Cheers, Lorenzo
> 


      reply	other threads:[~2026-08-31 16:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  8:28 Dev Jain
2026-08-31  8:47 ` Lorenzo Stoakes (ARM)
2026-08-31  9:13 ` Lance Yang
2026-08-31 15:59 ` Kunwu Chan
2026-08-31 16:00   ` Lorenzo Stoakes (ARM)
2026-08-31 16:41     ` Kunwu Chan [this message]

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=20260831164143.2517715-1-kunwu.chan@linux.dev \
    --to=kunwu.chan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=harry@kernel.org \
    --cc=jannh@google.com \
    --cc=kunwu.chan@linux.dev \
    --cc=lance.yang@linux.dev \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=riel@surriel.com \
    --cc=vbabka@kernel.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

all inboxes | Powered by JetHome®