From: Andrew Morton <akpm@linux-foundation.org>
To: Yichong Chen <chenyichong@uniontech.com>
Cc: vishal.moola@gmail.com, ye.liu@linux.dev, zhen.ni@easystack.cn,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/3] tools/mm/page_owner_sort: fix filtering and cleanup issues
Date: Sun, 28 Jun 2026 21:41:14 -0700 [thread overview]
Message-ID: <20260628214114.2ffe4c4ce7ce1ffa0e3338f2@linux-foundation.org> (raw)
In-Reply-To: <20260629014316.130307-1-chenyichong@uniontech.com>
On Mon, 29 Jun 2026 09:43:13 +0800 Yichong Chen <chenyichong@uniontech.com> wrote:
> Resend the page_owner_sort cleanup series with corrected threading.
>
> This version replaces the single patch currently queued in mm-new by
> splitting the cleanup into smaller patches and adding the search_pattern()
> bounds fix.
>
> Patch 1 renames is_need() to filter_record() and makes the filter path
> return explicit results. Patch 2 fixes the per-record allocation leaks.
> Patch 3 bounds search_pattern() output copies, addressing the pre-existing
> issue reported by Sashiko/AI review.
Thanks, I'll add this for testing and further review.
It looks like AI review found a minorish issue:
https://sashiko.dev/#/patchset/20260629014316.130307-1-chenyichong@uniontech.com
next prev parent reply other threads:[~2026-06-29 4:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 1:43 [PATCH v5 0/3] tools/mm/page_owner_sort: fix filtering and cleanup issues Yichong Chen
2026-06-29 1:43 ` [PATCH v5 1/3] tools/mm/page_owner_sort: return explicit filter results Yichong Chen
2026-06-29 1:43 ` [PATCH v5 2/3] tools/mm/page_owner_sort: free per-record allocations Yichong Chen
2026-06-29 1:43 ` [PATCH v5 3/3] tools/mm/page_owner_sort: bound pattern output copies Yichong Chen
2026-06-29 4:41 ` Andrew Morton [this message]
2026-06-29 6:25 ` [PATCH] tools/mm/page_owner_sort: report get_comm failures at source Yichong Chen
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=20260628214114.2ffe4c4ce7ce1ffa0e3338f2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chenyichong@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vishal.moola@gmail.com \
--cc=ye.liu@linux.dev \
--cc=zhen.ni@easystack.cn \
/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