Re: mm: call the security_mmap_file() LSM hook in remap_file_pages()

["yao.zhang1@amlogic.com" <yao.zhang1@amlogic.com>]

Hi gregkh

> original commit:
ea7e2d5e49c05e5db1922387b09ca74aa40f46e2
If use the original commit, there will be conflicts
 that need to be resolved manually.

> Then you have tested this already?  Also what will they do in December?
The customer currently plans to use only 5.15.

I`d like to ask a few questions:
1, What is a "tested backport"?
Is this for verifying code BUILD and kernel bootup?
or
Reproduce the issue and verify that the patch is effective?

2, How should I provide the "tested backport" to you?
As a patch file?
or
as a link?


Thanks,
-------------------------------
From: gregkh



Date: 2026-10-27 14:50



To: yao.zhang1@amlogic.com



CC: stable; tuan.zhang; jianxin.pan



Subject: Re: mm: call the security_mmap_file() LSM hook in remap_file_pages()



[ EXTERNAL EMAIL ]



 



On Tue, Oct 27, 2026 at 02:44:41PM +0800, yao.zhang1@amlogic.com wrote:



> Hi gregkh



>



> I have verified the following:



>



> 1. The patch can be applied to the `linux-5.15.y` branch.



> The commit applies cleanly on top of v5.15.223



> (using `git cherry-pick -x`, with no conflicts):



>



> git cherry-pick -x 0f910dbf2f2a4a7820ba4bac7b280f7108aa05b1



> with no conflicts





But that is not the original commit, please do this on the original.





And again, please provide a tested backport and we will be glad to



include it.





> 2. Our customer is using the `5.15.y` branch



> The customer has requested the inclusion of these CVEs.



> and is unwilling to upgrade to version 6.x or higher.





Then you have tested this already?  Also what will they do in December?





> Furthermore, as they are using GKI 2.0, they cannot apply "autopatch."



> the only way to incorporate fixes for CVEs is by updating the LTS.





I have no idea what this means at all, sorry.



greg k-h