From: Leon Hwang <leon.hwang@linux.dev>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, akpm@linux-foundation.org,
david@redhat.com, lorenzo.stoakes@oracle.com, shuah@kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Lance Yang <lance.yang@linux.dev>
Subject: Re: [PATCH 6.1.y] selftests/mm: Move default_huge_page_size to vm_util.c
Date: Wed, 22 Oct 2025 23:35:05 +0800 [thread overview]
Message-ID: <f1e5a58b-f5a5-4acb-85ea-59a7f43c060f@linux.dev> (raw)
In-Reply-To: <2025102241-clubbed-smirk-8819@gregkh>
On 2025/10/22 22:26, Greg KH wrote:
> On Wed, Oct 22, 2025 at 09:34:52PM +0800, Leon Hwang wrote:
>>
>>
>> On 2025/10/22 16:20, Greg KH wrote:
[...]
>>
>> Hi Greg,
>>
>> After checking with 'git blame map_hugetlb.c', the issue was introduced
>> by commit a584c7734a4d (“selftests: mm: fix map_hugetlb failure on 64K
>> page size systems”), which corresponds to upstream commit 91b80cc5b39f.
>> This change appears to have caused the build error in the 6.1.y tree.
>>
>> Comparing several stable trees shows the following:
>>
>> - 6.0.y: not backported*
>> - 6.1.y: backported
>> - 6.2.y: not backported*
>> - 6.3.y: not backported*
>> - 6.4.y: not backported*
>> - 6.5.y: not backported*
>> - 6.6.y: backported
>> - 6.7.y: backported
>>
>> Given this, it might be preferable to revert a584c7734a4d in 6.1.y for
>> consistency with the other stable trees (6.0.y, 6.2–6.5.y).
>
> Ah, yeah, it looks like this commit was reverted from other stable
> releases, as it shows up in the following releases:
>
> 4.19.310 4.19.315 5.4.272 5.4.277 5.10.213 5.10.218 5.15.152 5.15.160 6.1.82 6.6.18 6.7.6
>
> So a revert would be fine, want to submit it?
>
Got it. I'll send a patch to revert it later.
Thanks,
Leon
prev parent reply other threads:[~2025-10-22 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 5:51 Leon Hwang
2025-10-22 6:01 ` Lance Yang
2025-10-22 6:07 ` Greg KH
2025-10-22 6:20 ` Leon Hwang
2025-10-22 7:35 ` Greg KH
2025-10-22 7:40 ` Greg KH
2025-10-22 8:08 ` Leon Hwang
2025-10-22 8:20 ` Greg KH
2025-10-22 13:34 ` Leon Hwang
2025-10-22 14:26 ` Greg KH
2025-10-22 15:35 ` Leon Hwang [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=f1e5a58b-f5a5-4acb-85ea-59a7f43c060f@linux.dev \
--to=leon.hwang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=greg@kroah.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=shuah@kernel.org \
--cc=stable@vger.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