From: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
To: Chris Down <chris@chrisdown.name>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"David Hildenbrand (Arm)" <david@kernel.org>,
Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>,
Lance Yang <lance.yang@linux.dev>,
Matthew Wilcox <willy@infradead.org>,
Suren Baghdasaryan <surenb@google.com>,
Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH mm-hotfixes] mm/huge_memory: fix memory corruption on huge zero page move
Date: Mon, 9 Mar 2026 13:10:41 +0000 [thread overview]
Message-ID: <aca15b45-24b0-41df-be16-211bcb94ec79@lucifer.local> (raw)
In-Reply-To: <aaw-8SNI6FK14yxu@chrisdown.name>
On Sat, Mar 07, 2026 at 11:06:25PM +0800, Chris Down wrote:
> Thanks folks for sorting this one out, and my apologies for not being more
> responsive. I'm in south eastern China in a remote area until tomorrow and
> don't have internet in any form most of the time. The end results looks good
> to me.
That is a... very valid excuse tbf :>) hope you're having fun out there!
>
> For context, the reason I originally split it into two patches even though
> the second supercedes the first was to make sure Fixes: can match up to the
> right offending commits. But it is true that it may not be important.
Ack :)
>
> As for the threading, clearly I haven't been using git format-email enough.
> :-) And my apologies for neglecting to cc folks from get_maintainers.
Thanks :) sorry was probably overly grumpy in my reply, grump levels are
variable during the day/week ;)
>
> The end result looks good to me.
Great! Really wanted to make sure YOUR patch was the one that landed correctly
attributed, and of course to take into account the feedback from David, so I
think the end result fixes the issue and achieves all that.
Cheers, Lorenzo
prev parent reply other threads:[~2026-03-09 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 17:06 Lorenzo Stoakes
2026-03-02 17:10 ` David Hildenbrand (Arm)
2026-03-02 17:19 ` Lorenzo Stoakes
2026-03-02 20:50 ` Andrew Morton
2026-03-03 7:25 ` Lorenzo Stoakes
2026-03-03 8:49 ` David Hildenbrand (Arm)
2026-03-04 1:42 ` Andrew Morton
2026-03-04 11:41 ` Lorenzo Stoakes (Oracle)
2026-03-07 15:06 ` Chris Down
2026-03-09 13:10 ` Lorenzo Stoakes (Oracle) [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=aca15b45-24b0-41df-be16-211bcb94ec79@lucifer.local \
--to=ljs@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chris@chrisdown.name \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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