From: Andrew Morton <akpm@linux-foundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH v1 0/5] MM_CID and HPCC mm_struct static init fixes
Date: Mon, 22 Dec 2025 17:59:57 -0800 [thread overview]
Message-ID: <20251222175957.bfc9cf8b25e587f3f5e304bc@linux-foundation.org> (raw)
In-Reply-To: <20251221232926.450602-1-mathieu.desnoyers@efficios.com>
On Sun, 21 Dec 2025 18:29:21 -0500 Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> Mark Brown reported a regression [1] on linux next due to the
> hierarchical percpu counters (HPCC). You mentioned they were only in
> mm-new (and therefore not pulled into -next) [2], but it looks like they
> got more exposure that we expected. :)
We try to please ;)
Mark's report is why this series remains in mm-new and didn't get
promoted to mm-unstable (and hence linux-next).
Also, I anticipate a new version of this series thanks to
https://lkml.kernel.org/r/2fb78e41-5e56-425f-925f-a29524355d2c@efficios.com
> This bug hunting got me to fix static initialization issues in both
> MM_CID (for upstream) and HPCC (mm-new). Mark tested my series and
> confirmed that it fixes his issues.
>
> Please consider the HPCC fixes for mm-new, and the MM_CID fixes for
> upstream.
>
> This series is based on mm-new
> commit 287373d0b6ee ("selftests/mm: fix comment for check_test_requirements")
Well, simply appending this series to your "mm: Fix OOM killer
inaccuracy on large many-core systems, v10" will create an annoying
bisection hole.
Also, there are some cc:stable fixes in here which depend upon the
presence of "mm: Fix OOM killer inaccuracy on large many-core systems"
series, which is all backwards.
So for now I'll toss this series in there for testing but I'll ask for
a redo, please.
- All cc:stable patches prepared in a standalone fashion against
latest mainline.
- Any non-cc:stable patches which fix things in current mm-new come
next. Perhaps view these as preparation for "mm: Fix OOM killer
inaccuracy on large many-core systems".
- Then "mm: Fix OOM killer inaccuracy on large many-core systems,
v11" which incorporates anything which didn't make it into the above
two categories.
That could be as many as three patch series. Thanks.
next prev parent reply other threads:[~2025-12-23 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 23:29 Mathieu Desnoyers
2025-12-21 23:29 ` [PATCH v1 1/5] mm: Add missing static initializer for init_mm::mm_cid.lock Mathieu Desnoyers
2025-12-21 23:29 ` [PATCH v1 2/5] mm: Rename cpu_bitmap field to flexible_array Mathieu Desnoyers
2025-12-21 23:29 ` [PATCH v1 3/5] mm: Take into account mm_cid size for mm_struct static definitions Mathieu Desnoyers
2025-12-21 23:29 ` [PATCH v1 4/5] mm: Take into account hierarchical percpu tree items for static mm_struct definitions Mathieu Desnoyers
2025-12-21 23:29 ` [PATCH v1 5/5] tsacct: Skip all kernel threads Mathieu Desnoyers
2025-12-23 1:59 ` Andrew Morton [this message]
2025-12-24 16:37 ` [PATCH v1 0/5] MM_CID and HPCC mm_struct static init fixes Mathieu Desnoyers
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=20251222175957.bfc9cf8b25e587f3f5e304bc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mathieu.desnoyers@efficios.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