From: Wei Yang <richard.weiyang@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, baohua@kernel.org,
baolin.wang@linux.alibaba.com, david@kernel.org,
dev.jain@arm.com, lance.yang@linux.dev, liam.howlett@oracle.com,
lorenzo.stoakes@oracle.com, npache@redhat.com,
ryan.roberts@arm.com, stable@vger.kernel.org, ziy@nvidia.com
Subject: Re: FAILED: patch "[PATCH] mm/huge_memory: merge uniform_split_supported() and" failed to apply to 6.18-stable tree
Date: Sat, 3 Jan 2026 01:32:15 +0000 [thread overview]
Message-ID: <20260103013215.lvkskim32cvtm2b6@master> (raw)
In-Reply-To: <2026010206-footprint-impure-82b8@gregkh>
On Fri, Jan 02, 2026 at 01:24:28PM +0100, Greg KH wrote:
>On Tue, Dec 30, 2025 at 03:11:35AM +0000, Wei Yang wrote:
>> On Mon, Dec 29, 2025 at 01:33:25PM +0100, gregkh@linuxfoundation.org wrote:
>> >
>> >The patch below does not apply to the 6.18-stable tree.
>> >If someone wants it applied there, or to any other stable or longterm
>> >tree, then please email the backport, including the original git commit
>> >id to <stable@vger.kernel.org>.
>> >
>> >To reproduce the conflict and resubmit, you may use the following commands:
>> >
>> >git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.18.y
>> >git checkout FETCH_HEAD
>> >git cherry-pick -x 8a0e4bdddd1c998b894d879a1d22f1e745606215
>> ># <resolve conflicts, build, test, etc.>
>> >git commit -s
>> >git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2025122925-victory-numeral-2346@gregkh' --subject-prefix 'PATCH 6.18.y' HEAD^..
>> >
>> >Possible dependencies:
>> >
>> >
>>
>> Hi, Greg
>>
>> This one is not a fix to some bug.
>>
>> We found a real bug during the mail discussion, which is
>>
>> commit cff47b9e39a6abf03dde5f4f156f841b0c54bba0
>> Author: Wei Yang <richard.weiyang@gmail.com>
>> Date: Wed Nov 19 23:53:02 2025 +0000
>>
>> mm/huge_memory: fix NULL pointer deference when splitting folio
>>
>> It looks has been back ported to 6.18.y and 6.12.y.
>
>I do not understand, should this not be applied? Or should it be
>applied?
Upstream commit
cff47b9e39a6 2025-11-24 mm/huge_memory: fix NULL pointer deference when splitting folio
should be applied and already applied to 6.18.y and 6.12.y.
Upstream commit
8a0e4bdddd1c 2025-11-24 mm/huge_memory: merge uniform_split_supported() and non_uniform_split_supported()
is not necessary to be back ported.
>
>confused,
>
>greg k-h
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2026-01-03 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 12:33 FAILED: patch "[PATCH] mm/huge_memory: merge uniform_split_supported() and" failed to apply to 6.18-stable tree gregkh
2025-12-30 2:48 ` [PATCH 6.18.y] mm/huge_memory: merge uniform_split_supported() and non_uniform_split_supported() Sasha Levin
2025-12-30 3:11 ` FAILED: patch "[PATCH] mm/huge_memory: merge uniform_split_supported() and" failed to apply to 6.18-stable tree Wei Yang
2026-01-02 12:24 ` Greg KH
2026-01-03 1:32 ` Wei Yang [this message]
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=20260103013215.lvkskim32cvtm2b6@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=lance.yang@linux.dev \
--cc=liam.howlett@oracle.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=stable@vger.kernel.org \
--cc=ziy@nvidia.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