From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Mani Tofigh <mt4022@columbia.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <liam@infradead.org>,
Nico Pache <nico.pache@linux.dev>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
Usama Arif <usama.arif@linux.dev>,
Kiryl Shutsemau <kas@kernel.org>,
Shakeel Butt <shakeel.butt@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
"Lorenzo Stoakes (Oracle)" <ljs@kernel.org>,
Kairui Song <kasong@tencent.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
tz2294@columbia.edu, stable@vger.kernel.org
Subject: Re: [PATCH] mm/huge_memory: fix deferred split list corruption on partial unmap
Date: Tue, 27 Oct 2026 19:49:17 +0100 [thread overview]
Message-ID: <3f289ead-62fa-43b5-9d9f-790d94951822@kernel.org> (raw)
In-Reply-To: <CAE2e9Owov22KK3ZPkfqwrJFpAMc_H5Qq22aoKpQ=0mWhiX5Q_Q@mail.gmail.com>
On 10/27/26 17:47, Mani Tofigh wrote:
> Ouch, sorry about that, it was not intentional. I searched for similar reports a
> couple of hours before posting, but missed yours since it went out about an hour
> before mine. Your version is actually the better fix (more on that in your
> thread), so please drop this one.
Yeah, sorry, I was jumping to "this is an AI agent that rewrites fixes" too soon :)
Thanks for reporting the issue. Please do keep reporting such things (and
proposing fixes!)!
--
Cheers,
David
prev parent reply other threads:[~2026-10-27 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 0:22 Mani Tofigh via B4 Relay
2026-10-27 4:40 ` Lance Yang
2026-10-27 9:01 ` David Hildenbrand (Arm)
2026-10-27 16:47 ` Mani Tofigh
2026-10-27 18:49 ` David Hildenbrand (Arm) [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=3f289ead-62fa-43b5-9d9f-790d94951822@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=kas@kernel.org \
--cc=kasong@tencent.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mt4022@columbia.edu \
--cc=nico.pache@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=tz2294@columbia.edu \
--cc=usama.arif@linux.dev \
--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
all inboxes | Powered by JetHome®