public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: theflamefire89@gmail.com
Cc: stable@vger.kernel.org, James Morris <jmorris@namei.org>
Subject: Re: [PATCH 1/2] security: introduce CONFIG_SECURITY_WRITABLE_HOOKS
Date: Sun, 10 Jul 2022 15:26:45 +0200	[thread overview]
Message-ID: <YsrTlX6MHQWazszI@kroah.com> (raw)
In-Reply-To: <20220710131055.12934-1-theflamefire89@gmail.com>

On Sun, Jul 10, 2022 at 03:10:54PM +0200, theflamefire89@gmail.com wrote:
> From: James Morris <jmorris@namei.org>
> 
> commit dd0859dccbe291cf8179a96390f5c0e45cb9af1d upstream.
> 
> Subsequent patches will add RO hardening to LSM hooks, however, SELinux
> still needs to be able to perform runtime disablement after init to handle
> architectures where init-time disablement via boot parameters is not feasible.
> 
> Introduce a new kernel configuration parameter CONFIG_SECURITY_WRITABLE_HOOKS,
> and a helper macro __lsm_ro_after_init, to handle this case.
> 
> Signed-off-by: James Morris <james.l.morris@oracle.com>
> Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
> Acked-by: Casey Schaufler <casey@schaufler-ca.com>
> Acked-by: Kees Cook <keescook@chromium.org>
> Signed-off-by: Alexander Grund <git@grundis.de>
> ---
>  include/linux/lsm_hooks.h | 7 +++++++
>  security/Kconfig          | 5 +++++
>  security/selinux/Kconfig  | 6 ++++++
>  3 files changed, 18 insertions(+)

What kernel version(s) are you wanting this applied to?

And your email send address does not match your signed-off-by
name/address, so for obvious reasons, we can't take this.

thanks,

greg k-h

  parent reply	other threads:[~2022-07-10 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-10 13:10 [PATCH 1/2] security: introduce CONFIG_SECURITY_WRITABLE_HOOKS theflamefire89
2022-07-10 13:10 ` [PATCH 2/2] security: mark LSM hooks as __ro_after_init theflamefire89
2022-07-10 13:26 ` Greg KH [this message]
2022-07-10 13:27   ` [PATCH 1/2] security: introduce CONFIG_SECURITY_WRITABLE_HOOKS Greg KH
2022-07-10 14:08     ` Alexander Grund
2022-07-10 14:15       ` 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=YsrTlX6MHQWazszI@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jmorris@namei.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