From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>
Cc: Dev Jain <dev.jain@arm.com>,
akpm@linux-foundation.org, axelrasmussen@google.com,
yuanchu@google.com, weixugc@google.com, Liam.Howlett@oracle.com,
vbabka@suse.cz, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, riel@surriel.com, harry.yoo@oracle.com,
jannh@google.com, ryan.roberts@arm.com, baohua@kernel.org,
baolin.wang@linux.alibaba.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH mm-unstable] mm: Fix uffd-wp bit loss when batching file folio unmapping
Date: Fri, 16 Jan 2026 11:12:05 +0000 [thread overview]
Message-ID: <2f35393c-488c-4d3e-9f85-3e548fa32f69@lucifer.local> (raw)
In-Reply-To: <9edeeef1-5553-406b-8e56-30b11809eec5@kernel.org>
On Fri, Jan 16, 2026 at 11:57:46AM +0100, David Hildenbrand (Red Hat) wrote:
>
> That should likely be factored out in an independent patch.
>
> And while we do that, we should likely rename the function to indicate that
> we consume ptes.
>
> That patch should also describe why the change is ok; it's not just simple
> code movement. :)
Right, but this patch is to correct something in a series that's not yet
landed, it's not a hotfix, rather this should be a report on Baolin's
series rather than splitting the converastion into the actual thread where
Dev found an issue and an invalid patch submission here.
Can we try to get the conversation over there? Feel like maybe it's already
messed up... sigh.
>
> --
> Cheers
>
> David
Thanks, Lorenzo
prev parent reply other threads:[~2026-01-16 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 8:27 Dev Jain
2026-01-16 8:39 ` Lorenzo Stoakes
2026-01-16 9:40 ` Dev Jain
2026-01-16 9:48 ` Lorenzo Stoakes
2026-01-16 9:54 ` Dev Jain
2026-01-16 10:51 ` David Hildenbrand (Red Hat)
2026-01-17 17:46 ` Andrew Morton
2026-01-16 10:57 ` David Hildenbrand (Red Hat)
2026-01-16 11:12 ` Lorenzo Stoakes [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=2f35393c-488c-4d3e-9f85-3e548fa32f69@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=harry.yoo@oracle.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
/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