From: Andrew Morton <akpm@linux-foundation.org>
To: Muchun Song <muchun.song@linux.dev>
Cc: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>,
"Muchun Song" <songmuchun@bytedance.com>,
"David Hildenbrand" <david@kernel.org>,
"Oscar Salvador" <osalvador@suse.de>,
"Dave Hansen" <dave.hansen@intel.com>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Kevin Brodsky" <kevin.brodsky@arm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Alistair Popple" <apopple@nvidia.com>,
linux-mm@kvack.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/4] mm: fix missing page-table destructor in pagetable_free()
Date: Mon, 12 Oct 2026 20:25:32 -0700 [thread overview]
Message-ID: <20261012202532.f059fd5ab947510a21d34cd1@linux-foundation.org> (raw)
In-Reply-To: <200A83B9-233C-44C7-B4AF-0900BA1E09DF@linux.dev>
On Tue, 13 Oct 2026 10:50:21 +0800 Muchun Song <muchun.song@linux.dev> wrote:
> >> The correct trailer is:
> >>
> >> Cc: <stable@vger.kernel.org> # 6.16-6.18: bf9e4e30f353: x86/mm: use pagetable_free()
> >>
> >> Andrew, would you be able to update the trailer in the patch when you
> >> pick it up? If there are further review comments that require code
> >> changes, I'll fix this trailer as part of the v3 respin. Thanks a lot!
> >
> > I don't know if/how the -stable maintainers handle a comment like that.
> > I expect it's more reliable to do this via Fixes:. Possible?
> >
>
> Thanks. I used this format because it is explicitly documented by the
> stable kernel rules.
>
> The shell-style comment is the format documented in
> Documentation/process/stable-kernel-rules.rst for specifying additional
> patch prerequisites:
>
> Cc: <stable@vger.kernel.org> # 3.3.x: <commit>: <subject>
> Cc: <stable@vger.kernel.org> # 3.3.x
>
> See:
>
> https://docs.kernel.org/process/stable-kernel-rules.html#option-1
Oh. Consider me educated. Edited.
> A Fixes tag alone cannot express this dependency. It does not specify
> an additional commit that must be cherry-picked first. The documented
> Cc comment provides both the prerequisite and the required cherry-pick
> order.
>
> Would this be sufficient for the stable team to pick up the prerequisite?
Hopefully. I suggest you double-check when you get the emails as these
are applied to the various stable trees.
next prev parent reply other threads:[~2026-10-13 3:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 11:24 [PATCH v2 0/4] mm: Fix page-table teardown during memory hot-remove Muchun Song
2026-10-10 11:24 ` [PATCH v2 1/4] mm: fix missing page-table destructor in pagetable_free() Muchun Song
2026-10-12 11:15 ` Jose A. Perez de Azpillaga
2026-10-12 12:55 ` Muchun Song
2026-10-12 17:21 ` Jose A. Perez de Azpillaga
2026-10-13 6:33 ` Muchun Song
2026-10-13 2:31 ` Andrew Morton
2026-10-13 2:50 ` Muchun Song
2026-10-13 3:25 ` Andrew Morton [this message]
2026-10-13 6:26 ` Muchun Song
2026-10-12 13:27 ` David Hildenbrand (Arm)
2026-10-12 13:29 ` Muchun Song
2026-10-12 14:06 ` Dave Hansen
2026-10-10 11:24 ` [PATCH v2 2/4] riscv/mm: fix hotplug page-table destructor handling Muchun Song
2026-10-12 13:28 ` David Hildenbrand (Arm)
2026-10-12 15:32 ` Björn Töpel
2026-10-10 11:24 ` [PATCH v2 3/4] riscv/mm: fix missing destructor for hotplug PUD tables Muchun Song
2026-10-12 15:35 ` Björn Töpel
2026-10-10 11:24 ` [PATCH v2 4/4] arm64/mm: fix destructor for unconstructed hotplug page tables Muchun Song
2026-10-12 13:30 ` 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=20261012202532.f059fd5ab947510a21d34cd1@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=agordeev@linux.ibm.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=apopple@nvidia.com \
--cc=azpijr@gmail.com \
--cc=bjorn@rivosinc.com \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@intel.com \
--cc=david@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=stable@vger.kernel.org \
--cc=will@kernel.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®