From: Mark Brown <broonie@kernel.org>
To: Lorenzo Stoakes <ljs@kernel.org>
Cc: Mike Rapoport <rppt@kernel.org>,
"Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
"David Hildenbrand (Arm)" <david@kernel.org>,
Nico Pache <npache@redhat.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, liam@infradead.org, mhocko@suse.com,
vbabka@suse.cz, willy@infradead.org
Subject: Re: Process (was Re: [PATCH mm-hotfixes-unstable v18 00/14] khugepaged: add mTHP) collapse support
Date: Wed, 3 Jun 2026 10:03:37 +0100 [thread overview]
Message-ID: <ecf71d71-5d20-49c2-8b19-e76ec9353585@sirena.org.uk> (raw)
In-Reply-To: <ah_ML-Wm3B92ZniC@lucifer>
[-- Attachment #1: Type: text/plain, Size: 1872 bytes --]
On Wed, Jun 03, 2026 at 07:48:46AM +0100, Lorenzo Stoakes wrote:
> On Tue, Jun 02, 2026 at 08:31:42PM +0300, Mike Rapoport wrote:
> > * Supposing we keep the model of early merging for testing [Lorenzo, don't
> > yell at me ;-)] I think it's reasonable enough to drop everything that's
> > not going upstream at, say, rc6 and ask contributors to rinse and repeat
> > after rc1.
> I won't yell :) but I really don't want us to do this, and to improve our
> testing locally. Because:
> - We've become a bit notorious for breaking linux-next
TBH I can't say I've registered that with either of my running linux-next
or my testing hats on. Considering the scope of what ends up in the mm
tree it's not particularly concerning, and it's very rare for there to be
anything so catastrophically bad at runtime that it causes unreasonable
disruption. Importantly when there are issues they tend to get addressed
promptly with either a fix or dropping the offending code as far as I can
see, that's key for -next.
If you're looking at -next you're looking to provide early testing so
breakage is expected, there's a balance with making an effort to ensure
that you don't make too much noise for people doing testing and especially
avoiding causing too much breakage which means things don't run at all.
Of course having written the above there's a -mm build failure today.
> - It makes it more difficult for us to yank things
FWIW I can easily add extra trees to -next, and there's the option of
doing something like the fs-current and fs-next branches in -next ATM
where I do submerges consisting of only the various filesystem trees
which are published separately so they can be used for filesystem
specific testing. There's several areas where integration trees require
their subtrees to be in -next directly for a bit before they get merged
into the integration tree.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-06-03 9:03 UTC|newest]
Thread overview: 145+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 14:59 [PATCH mm-hotfixes-unstable v18 00/14] khugepaged: add mTHP " Nico Pache
2026-05-22 14:59 ` [PATCH mm-unstable v18 01/14] mm/khugepaged: generalize hugepage_vma_revalidate for mTHP support Nico Pache
2026-05-22 14:59 ` [PATCH mm-unstable v18 02/14] mm/khugepaged: generalize alloc_charge_folio() Nico Pache
2026-05-22 14:59 ` [PATCH mm-unstable v18 03/14] mm/khugepaged: rework max_ptes_* handling with helper functions Nico Pache
2026-05-22 21:16 ` David Hildenbrand (Arm)
2026-06-01 13:26 ` Lorenzo Stoakes
2026-06-05 16:04 ` Zi Yan
2026-05-22 14:59 ` [PATCH mm-unstable v18 04/14] mm/khugepaged: generalize __collapse_huge_page_* for mTHP support Nico Pache
2026-05-22 21:24 ` David Hildenbrand (Arm)
2026-05-26 14:39 ` Nico Pache
2026-06-01 14:04 ` Lorenzo Stoakes
2026-05-22 15:00 ` [PATCH mm-unstable v18 05/14] mm/khugepaged: require collapse_huge_page to enter/exit with the lock dropped Nico Pache
2026-06-01 14:07 ` Lorenzo Stoakes
2026-06-02 10:26 ` Nico Pache
2026-05-22 15:00 ` [PATCH mm-unstable v18 06/14] mm/khugepaged: generalize collapse_huge_page for mTHP collapse Nico Pache
2026-05-22 21:47 ` David Hildenbrand (Arm)
2026-05-26 14:42 ` Nico Pache
2026-05-31 9:39 ` Lance Yang
2026-05-31 20:00 ` David Hildenbrand (Arm)
2026-06-01 3:28 ` Lance Yang
2026-06-01 6:54 ` David Hildenbrand (Arm)
2026-06-01 7:49 ` Lance Yang
2026-06-01 8:15 ` David Hildenbrand (Arm)
2026-06-01 8:44 ` Lance Yang
2026-06-01 10:09 ` David Hildenbrand (Arm)
2026-06-01 9:08 ` Lance Yang
2026-06-01 10:23 ` David Hildenbrand (Arm)
2026-06-01 10:47 ` Lance Yang
2026-06-01 11:13 ` David Hildenbrand (Arm)
2026-06-01 15:00 ` Nico Pache
2026-06-01 15:05 ` David Hildenbrand (Arm)
2026-06-01 16:07 ` Lance Yang
2026-06-04 17:04 ` Nico Pache
2026-06-04 18:12 ` Lorenzo Stoakes
2026-06-05 7:18 ` David Hildenbrand (Arm)
2026-06-05 8:07 ` Lorenzo Stoakes
2026-06-05 8:59 ` Lance Yang
2026-06-02 15:30 ` Nico Pache
2026-06-02 16:34 ` Lance Yang
2026-06-04 12:33 ` Lorenzo Stoakes
2026-06-04 10:21 ` Lorenzo Stoakes
2026-06-04 10:32 ` Nico Pache
2026-06-04 11:38 ` Lorenzo Stoakes
2026-06-04 12:39 ` Lorenzo Stoakes
2026-06-04 12:45 ` Nico Pache
2026-06-04 12:55 ` Lorenzo Stoakes
2026-06-04 16:28 ` Nico Pache
2026-05-22 15:00 ` [PATCH mm-unstable v18 07/14] mm/khugepaged: skip collapsing mTHP to smaller orders Nico Pache
2026-05-22 21:51 ` David Hildenbrand (Arm)
2026-05-22 15:00 ` [PATCH mm-unstable v18 08/14] mm/khugepaged: add per-order mTHP collapse failure statistics Nico Pache
2026-05-31 20:09 ` David Hildenbrand (Arm)
2026-06-01 14:13 ` Lorenzo Stoakes
2026-05-22 15:00 ` [PATCH mm-unstable v18 09/14] mm/khugepaged: improve tracepoints for mTHP orders Nico Pache
2026-05-22 15:00 ` [PATCH mm-unstable v18 10/14] mm/khugepaged: introduce collapse_allowable_orders helper function Nico Pache
2026-05-31 20:18 ` David Hildenbrand (Arm)
2026-06-01 14:35 ` Lorenzo Stoakes
2026-06-01 14:40 ` David Hildenbrand (Arm)
2026-05-22 15:00 ` [PATCH mm-unstable v18 11/14] mm/khugepaged: Introduce mTHP collapse support Nico Pache
2026-05-25 14:15 ` Nico Pache
2026-05-25 19:10 ` Andrew Morton
2026-05-26 6:57 ` Wei Yang
2026-05-26 12:07 ` Nico Pache
2026-05-28 8:42 ` Wei Yang
2026-05-28 17:11 ` Nico Pache
2026-05-31 7:18 ` Lance Yang
2026-05-31 8:48 ` Lance Yang
2026-06-01 12:01 ` Nico Pache
2026-06-01 12:06 ` David Hildenbrand (Arm)
2026-06-02 10:58 ` Nico Pache
2026-06-02 15:44 ` Lance Yang
2026-06-03 8:05 ` David Hildenbrand (Arm)
2026-06-04 14:40 ` Lorenzo Stoakes
2026-06-01 8:11 ` David Hildenbrand (Arm)
2026-06-01 12:40 ` Nico Pache
2026-06-01 13:15 ` David Hildenbrand (Arm)
2026-06-02 17:23 ` Nico Pache
2026-06-02 17:26 ` Nico Pache
2026-06-03 9:55 ` David Hildenbrand (Arm)
2026-06-03 10:00 ` David Hildenbrand (Arm)
2026-06-03 12:16 ` Nico Pache
2026-06-03 12:27 ` David Hildenbrand (Arm)
2026-06-04 14:14 ` Lorenzo Stoakes
2026-06-04 14:19 ` Lorenzo Stoakes
2026-06-04 13:53 ` Lorenzo Stoakes
2026-06-04 13:59 ` Lorenzo Stoakes
2026-06-04 14:45 ` Lorenzo Stoakes
2026-06-05 11:07 ` Nico Pache
2026-06-05 11:08 ` Nico Pache
2026-05-22 15:00 ` [PATCH mm-unstable v18 12/14] mm/khugepaged: avoid unnecessary mTHP collapse attempts Nico Pache
2026-05-31 7:31 ` Lance Yang
2026-05-31 20:02 ` David Hildenbrand (Arm)
2026-06-01 1:53 ` Lance Yang
2026-05-22 15:00 ` [PATCH mm-unstable v18 13/14] mm/khugepaged: run khugepaged for all orders Nico Pache
2026-05-22 15:00 ` [PATCH mm-unstable v18 14/14] Documentation: mm: update the admin guide for mTHP collapse Nico Pache
2026-05-22 21:58 ` David Hildenbrand (Arm)
2026-05-26 12:00 ` Nico Pache
2026-05-26 14:45 ` Nico Pache
2026-05-22 15:07 ` [PATCH mm-hotfixes-unstable v18 00/14] khugepaged: add mTHP collapse support Nico Pache
2026-05-22 15:13 ` Vlastimil Babka (SUSE)
2026-05-22 16:11 ` Nico Pache
2026-05-22 21:13 ` David Hildenbrand (Arm)
2026-05-26 8:33 ` Process (was Re: [PATCH mm-hotfixes-unstable v18 00/14] khugepaged: add mTHP) " Lorenzo Stoakes
2026-05-26 19:09 ` Andrew Morton
2026-05-26 20:42 ` Vlastimil Babka (SUSE)
2026-05-31 19:49 ` David Hildenbrand (Arm)
2026-06-01 15:41 ` Lorenzo Stoakes
2026-06-01 15:45 ` David Hildenbrand (Arm)
2026-06-01 16:16 ` Lorenzo Stoakes
2026-06-02 11:20 ` David Hildenbrand (Arm)
2026-06-02 11:31 ` David Hildenbrand (Arm)
2026-06-02 12:47 ` Lorenzo Stoakes
2026-06-02 12:55 ` Vlastimil Babka (SUSE)
2026-06-02 13:01 ` David Hildenbrand (Arm)
2026-06-02 17:31 ` Mike Rapoport
2026-06-03 6:48 ` Lorenzo Stoakes
2026-06-03 8:39 ` Mike Rapoport
2026-06-03 9:57 ` Mark Brown
2026-06-03 10:51 ` Mike Rapoport
2026-06-03 9:03 ` Mark Brown [this message]
2026-06-02 12:40 ` Lorenzo Stoakes
2026-06-02 12:49 ` David Hildenbrand (Arm)
2026-06-02 12:47 ` Vlastimil Babka (SUSE)
2026-06-02 12:58 ` David Hildenbrand (Arm)
2026-06-02 13:08 ` Vlastimil Babka (SUSE)
2026-06-02 13:16 ` David Hildenbrand (Arm)
2026-06-03 1:48 ` SeongJae Park
2026-06-05 15:24 ` David Hildenbrand (Arm)
2026-06-06 0:01 ` SeongJae Park
2026-06-01 15:37 ` Lorenzo Stoakes
2026-06-01 15:43 ` David Hildenbrand (Arm)
2026-06-01 15:47 ` Lorenzo Stoakes
2026-06-01 16:00 ` David Hildenbrand (Arm)
2026-05-22 15:16 ` [PATCH mm-hotfixes-unstable v18 00/14] khugepaged: add mTHP " Lorenzo Stoakes
2026-05-22 16:08 ` Nico Pache
2026-05-22 16:19 ` Lorenzo Stoakes
2026-05-22 16:31 ` Nico Pache
2026-05-22 17:12 ` Lorenzo Stoakes
2026-05-26 8:14 ` Lorenzo Stoakes
2026-05-22 15:13 ` Lorenzo Stoakes
2026-05-22 20:47 ` Andrew Morton
2026-06-01 15:58 ` Alexander Gordeev
2026-06-01 17:05 ` Nico Pache
2026-06-01 17:08 ` Lorenzo Stoakes
2026-06-02 1:53 ` Lance Yang
2026-06-04 10:10 ` Lorenzo Stoakes
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=ecf71d71-5d20-49c2-8b19-e76ec9353585@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=npache@redhat.com \
--cc=rppt@kernel.org \
--cc=vbabka@kernel.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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®