[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250529204754.f3cd5d72cd68755e6753d378@linux-foundation.org>
Date: Thu, 29 May 2025 20:47:54 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Pu Lehui <pulehui@...weicloud.com>
Cc: mhiramat@...nel.org, oleg@...hat.com, peterz@...radead.org,
Liam.Howlett@...cle.com, lorenzo.stoakes@...cle.com, vbabka@...e.cz,
jannh@...gle.com, pfalcato@...e.de, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org, pulehui@...wei.com
Subject: Re: [PATCH v1 2/4] mm: Expose abnormal new_pte during move_ptes
On Fri, 30 May 2025 09:24:54 +0800 Pu Lehui <pulehui@...weicloud.com> wrote:
> > check that patch [1/4] is working? Perhaps VM_WARN_ON_ONCE() would be
>
> Agree, should I respin one more?
That's OK, I added this:
--- a/mm/mremap.c~mm-expose-abnormal-new_pte-during-move_ptes-fix
+++ a/mm/mremap.c
@@ -237,7 +237,7 @@ static int move_ptes(struct pagetable_mo
for (; old_addr < old_end; old_pte++, old_addr += PAGE_SIZE,
new_pte++, new_addr += PAGE_SIZE) {
- WARN_ON_ONCE(!pte_none(*new_pte));
+ VM_WARN_ON_ONCE(!pte_none(*new_pte));
if (pte_none(ptep_get(old_pte)))
continue;
_
Powered by blists - more mailing lists