From: Yang Shi <shy828301@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
syzbot+d1974fc28545a3e6218b@syzkaller.appspotmail.com,
David Hildenbrand <david@redhat.com>,
Will Deacon <will@kernel.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH v2] arm64: mte: Do not warn if the page is already tagged in copy_highpage()
Date: Wed, 22 Oct 2025 11:08:02 -0700 [thread overview]
Message-ID: <CAHbLzkoG7zXHubYoh3gSWkdmsLEsMDrBzdAuViRzTEwQNHkpNw@mail.gmail.com> (raw)
In-Reply-To: <20251022101704.4015055-1-catalin.marinas@arm.com>
On Wed, Oct 22, 2025 at 3:20 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_ONCE(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
> Reviewed-by: David Hildenbrand <david@redhat.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
> Cc: <stable@vger.kernel.org> # 6.12.x
> ---
>
> v2:
> - Also remove the WARN_ON_ONCE for hugetlb pages
> - Drop a double-underscore in the commit log
Reviewed-by: Yang Shi <yang@os.amperecomputing.com>
>
> arch/arm64/mm/copypage.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/mm/copypage.c b/arch/arm64/mm/copypage.c
> index a86c897017df..cd5912ba617b 100644
> --- a/arch/arm64/mm/copypage.c
> +++ b/arch/arm64/mm/copypage.c
> @@ -35,7 +35,7 @@ void copy_highpage(struct page *to, struct page *from)
> from != folio_page(src, 0))
> return;
>
> - WARN_ON_ONCE(!folio_try_hugetlb_mte_tagging(dst));
> + folio_try_hugetlb_mte_tagging(dst);
>
> /*
> * Populate tags for all subpages.
> @@ -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));
> + /*
> + * Most of the time it's a new page that shouldn't have been
> + * tagged yet. However, folio migration can end up reusing the
> + * same page without untagging it. Ignore the warning if the
> + * page is already tagged.
> + */
> + try_page_mte_tagging(to);
>
> mte_copy_page_tags(kto, kfrom);
> set_page_mte_tagged(to);
>
next prev parent reply other threads:[~2025-10-22 18:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 10:09 Catalin Marinas
2025-10-22 18:08 ` Yang Shi [this message]
2025-10-23 17:58 ` Catalin Marinas
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=CAHbLzkoG7zXHubYoh3gSWkdmsLEsMDrBzdAuViRzTEwQNHkpNw@mail.gmail.com \
--to=shy828301@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox