From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Kelvin Zhang <zhangxp1998@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, "Liam R . Howlett" <liam@infradead.org>,
Lorenzo Stoakes <ljs@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>,
Kalesh Singh <kaleshsingh@google.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] fs/proc/task_mmu: check THP exclusivity for each subpage
Date: Thu, 5 Nov 2026 20:40:21 +0100 [thread overview]
Message-ID: <ea17ea77-7238-4a78-88f4-7c9ec0528c4e@kernel.org> (raw)
In-Reply-To: <179355762314.2759535.4568050479263510899.pagemap-thp-repro@gmail.com>
On 11/1/26 19:27, Kelvin Zhang wrote:
> Hi David,
>
> Thanks for the clarification.
>
> I don't have a real application depending on precise per-subpage bit 56
> values, or a production failure to report. This is a review/test-driven
> report, with LLM assistance, rather than something found through a failing
> workload. I followed it up with an actual old/new kernel comparison.
Okay, thanks. I think it's best to just change the behavior to the new world
directly.
I'll respin my patch separately shortly, documenting your finding.
--
Cheers,
David
next prev parent reply other threads:[~2026-11-05 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 17:01 Kelvin Zhang
2026-11-01 18:07 ` David Hildenbrand (Arm)
2026-11-01 18:18 ` David Hildenbrand (Arm)
2026-11-01 18:27 ` Kelvin Zhang
2026-11-05 19:40 ` David Hildenbrand (Arm) [this message]
2026-11-01 19:02 ` Andrew Morton
2026-11-02 7:01 ` David Hildenbrand (Arm)
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=ea17ea77-7238-4a78-88f4-7c9ec0528c4e@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=kaleshsingh@google.com \
--cc=liam@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=pfalcato@suse.de \
--cc=stable@vger.kernel.org \
--cc=vbabka@kernel.org \
--cc=zhangxp1998@gmail.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®