All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Yang Shi <shy828301@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
	syzbot+d1974fc28545a3e6218b@syzkaller.appspotmail.com,
	Will Deacon <will@kernel.org>,
	David Hildenbrand <david@redhat.com>,
	Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH] arm64: mte: Do not warn if the page is already tagged in copy_highpage()
Date: Wed, 22 Oct 2025 10:57:52 +0100	[thread overview]
Message-ID: <aPiqoGyCmj7bA37C@arm.com> (raw)
In-Reply-To: <CAHbLzkpd8awNe=bZVv9fTux+Fx-HT8qL4ENZ-uC4YcPjf9e=KQ@mail.gmail.com>

On Tue, Oct 21, 2025 at 12:00:04PM -0700, Yang Shi wrote:
> On Tue, Oct 21, 2025 at 11:14 AM Catalin Marinas
> <catalin.marinas@arm.com> wrote:
> > The arm64 copy_highpage() assumes that the destination page is newly
> > allocated and not MTE-tagged (PG_mte_tagged unset) and warns
> > accordingly. However, following commit 060913999d7a ("mm: migrate:
> > support poisoned recover from migrate folio"), __folio_mc_copy() is
> > called before __folio_migrate_mapping(). If the latter fails (-EAGAIN),
> > the copy will be done again to the same destination page. Since
> > copy_highpage() already set the PG_mte_tagged flag, this second copy
> > will warn.
> >
> > Replace the WARN_ON(page already tagged) in the arm64 copy_highpage()
> > with a comment.
> >
> > Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> > Reported-by: syzbot+d1974fc28545a3e6218b@syzkaller.appspotmail.com
> > Link: https://lore.kernel.org/r/68dda1ae.a00a0220.102ee.0065.GAE@google.com
> > Cc: <stable@vger.kernel.org> # 6.12.x
> > Cc: Will Deacon <will@kernel.org>
> > Cc: David Hildenbrand <david@redhat.com>
> > Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
> > ---
> >  arch/arm64/mm/copypage.c | 9 +++++++--
> >  1 file changed, 7 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/arm64/mm/copypage.c b/arch/arm64/mm/copypage.c
> > index a86c897017df..40749d0a385c 100644
> > --- a/arch/arm64/mm/copypage.c
> > +++ b/arch/arm64/mm/copypage.c
> > @@ -51,8 +51,13 @@ void copy_highpage(struct page *to, struct page *from)
> >                 }
> >                 folio_set_hugetlb_mte_tagged(dst);
> >         } else if (page_mte_tagged(from)) {
> > -               /* It's a new page, shouldn't have been tagged yet */
> > -               WARN_ON_ONCE(!try_page_mte_tagging(to));
> 
> I think you should remove the WARN_ON_ONCE in the above hugetlb chunk
> too IIUC. migrate_huge_page_move_mapping() does the similar thing.

Good point. Thanks!

-- 
Catalin


      parent reply	other threads:[~2025-10-22  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21 18:13 [PATCH] arm64: mte: Do not warn if the page is already tagged in copy_highpage() Catalin Marinas
2025-10-21 18:23 ` David Hildenbrand
2025-10-21 19:00 ` Yang Shi
2025-10-22  6:19   ` Kefeng Wang
2025-10-22 10:00     ` Catalin Marinas
2025-10-22  9:57   ` Catalin Marinas [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=aPiqoGyCmj7bA37C@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=david@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=shy828301@gmail.com \
    --cc=syzbot+d1974fc28545a3e6218b@syzkaller.appspotmail.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.