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