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

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

Hi sashal , gregkh

1,  Based on 5.15.y, I tested these two patches; 
the kernel BUILD successfully and kernel bootup without any issues.

2,  Submitted two patches via `git send-email`.
ea7e2d5e49c0:
Message-ID: <20261028080719.1821-1-yao.zhang1@amlogic.com>

58a039e679fe:
Message-ID: <20261028080835.1852-1-yao.zhang1@amlogic.com>

Submit to
https://lore.kernel.org/stable/


Thanks, 


--------------


>[ EXTERNAL EMAIL ]



>



>> If use the original commit, there will be conflicts



>>  that need to be resolved manually.



>



>The original can't go to 5.15 on its own. ea7e2d5e49c0 ("mm: call the



>security_mmap_file() LSM hook in remap_file_pages()") calls



>security_mmap_file() under the mmap write lock, which creates a lock inversion



>with IMA. That is fixed by 58a039e679fe ("mm: split critical region in



>remap_file_pages() and invoke LSMs in between"). Greg dropped the earlier 5.15



>and 5.10 backports in February 2025 for leaving it out, and 6.1.y has carried



>the original without it since 6.1.120.



>



>I've queued 58a039e679fe for 6.1. For 5.15 the backport has to be the two



>commits as a pair: the original, then 58a039e679fe.



>



>> 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?



>



>At minimum, build and boot 5.15.y with both patches applied. If you can



>reproduce the original problem, please also confirm it is gone.



>



>> 2, How should I provide the "tested backport" to you?



>> As a patch file?



>> or



>> as a link?



>



>Send them inline with git send-email to stable@vger.kernel.org, one mail per



>patch, with [PATCH 5.15.y] in the subject. Each commit message needs the



>upstream commit ID and a note on anything you changed from it. See Option 3 in



>Documentation/process/stable-kernel-rules.rst.



>



>--



>Thanks,



>Sasha