From: gregkh <gregkh@linuxfoundation.org>
To: "yao.zhang1@amlogic.com" <yao.zhang1@amlogic.com>
Cc: stable <stable@vger.kernel.org>,
"tuan.zhang" <tuan.zhang@amlogic.com>,
"jianxin.pan" <jianxin.pan@amlogic.com>
Subject: Re: mm: call the security_mmap_file() LSM hook in remap_file_pages()
Date: Tue, 27 Oct 2026 07:50:20 +0100 [thread overview]
Message-ID: <2026102715-carry-strenuous-652d@gregkh> (raw)
In-Reply-To: <2026102714443948547539@amlogic.com>
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
next prev parent reply other threads:[~2026-10-27 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026102711371963416812@amlogic.com>
2026-10-27 5:50 ` mm: call the security_mmap_file() LSM hook in remap_file_pages() gregkh
2026-10-27 6:44 ` yao.zhang1
2026-10-27 6:50 ` gregkh [this message]
2026-10-27 8:56 ` yao.zhang1
2026-10-27 19:10 ` Sasha Levin
2026-10-28 8:31 ` yao.zhang1
2026-10-27 6:00 ` yao.zhang1
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=2026102715-carry-strenuous-652d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jianxin.pan@amlogic.com \
--cc=stable@vger.kernel.org \
--cc=tuan.zhang@amlogic.com \
--cc=yao.zhang1@amlogic.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