From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Grund <theflamefire89@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [GIT 4.9] LSM,security,selinux,smack: Backport of LSM changes
Date: Sat, 9 Jul 2022 14:16:10 +0200 [thread overview]
Message-ID: <YslxiluWV9YnPPAY@kroah.com> (raw)
In-Reply-To: <4230dd79-b64f-14e6-3614-02e4acb3f284@gmail.com>
On Sat, Jul 09, 2022 at 02:07:17PM +0200, Alexander Grund wrote:
> The following changes since commit 445514206988935e5ef0e80588d7481aa3cd3b7b:
>
> Linux 4.9.322 (2022-07-07 17:30:12 +0200)
>
> are available in the Git repository at:
>
> https://github.com/Flamefire/android_kernel_sony_msm8998.git lsm_hooks_backport_4.9
I can not take a git pull for stable patches, as my bot says:
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
Please just send them to us in patch form like all other stable
submissions.
> for you to fetch changes up to 911aa0e49633be52c7a2de8c99de87b6bf3a7604:
>
> LSM: Initialize security_hook_heads upon registration. (2022-07-09 12:51:42 +0200)
>
> All commits are cherry-picks/backports from mainline.
> The intend was to apply the last commit ("LSM: Initialize security_hook_heads upon registration.") with as few changes as possible.
Why?
> This revealed added/removed/changed hooks and related changes which seem valuable to have in 4.9 and via the CIP in 4.4 SLTS.
What is "CIP"?
> For additional Context: I initially backported those directly to CIPs v4.4-st14 and tested those on an ARM64 Android device from SONY. [1]
I have no context or understand this, sorry :(
thanks,
greg k-h
next prev parent reply other threads:[~2022-07-09 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 12:07 [GIT 4.9] LSM,security,selinux,smack: Backport of LSM changes Alexander Grund
2022-07-09 12:16 ` Greg KH [this message]
2022-07-10 10:44 ` Alexander Grund
2022-07-10 11:06 ` Greg KH
2022-07-10 12:38 ` Alexander Grund
2022-07-10 12:48 ` Greg KH
2022-07-10 13:02 ` Alexander Grund
2022-07-10 13:23 ` Greg KH
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=YslxiluWV9YnPPAY@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=theflamefire89@gmail.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