Re: [PATCH v2 1/4] mm: fix missing page-table destructor in pagetable_free()

[Muchun Song <muchun.song@linux.dev>]

> On Oct 13, 2026, at 11:25, Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> 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.

OK. I'll keep an eye on it.

Thanks.