From: Greg KH <gregkh@linuxfoundation.org>
To: Arulpandiyan Vadivel <arulpandiyan.vadivel@siemens.com>
Cc: linux-security-module@vger.kernel.org,
linux-modules@vger.kernel.org, stable@vger.kernel.org,
cedric.hombourger@siemens.com, srikanth.krishnakar@siemens.com
Subject: Re: [PATCH] loadpin: remove MODULE_COMPRESS_NONE as it is no longer supported
Date: Mon, 13 Jan 2025 11:19:28 +0100 [thread overview]
Message-ID: <2025011322-climatic-rotting-5b03@gregkh> (raw)
In-Reply-To: <20250113093115.72619-1-arulpandiyan.vadivel@siemens.com>
On Mon, Jan 13, 2025 at 03:01:15PM +0530, Arulpandiyan Vadivel wrote:
> Commit c7ff693fa2094ba0a9d0a20feb4ab1658eff9c33 ("module: Split
> modules_install compression and in-kernel decompression") removed the
> MODULE_COMPRESS_NONE, but left it loadpin's Kconfig, and removing it
>
> Signed-off-by: Arulpandiyan Vadivel <arulpandiyan.vadivel@siemens.com>
> ---
> security/loadpin/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/security/loadpin/Kconfig b/security/loadpin/Kconfig
> index 848f8b4a60190..94348e2831db9 100644
> --- a/security/loadpin/Kconfig
> +++ b/security/loadpin/Kconfig
> @@ -16,7 +16,7 @@ config SECURITY_LOADPIN_ENFORCE
> depends on SECURITY_LOADPIN
> # Module compression breaks LoadPin unless modules are decompressed in
> # the kernel.
> - depends on !MODULES || (MODULE_COMPRESS_NONE || MODULE_DECOMPRESS)
> + depends on !MODULES || MODULE_DECOMPRESS
> help
> If selected, LoadPin will enforce pinning at boot. If not
> selected, it can be enabled at boot with the kernel parameter
> --
> 2.39.5
>
>
<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>
next prev parent reply other threads:[~2025-01-13 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 9:31 [PATCH] loadpin: remove MODULE_COMPRESS_NONE as it is no longer supported Arulpandiyan Vadivel
2025-01-13 10:19 ` Greg KH [this message]
2025-01-13 13:42 ` Petr Pavlu
-- strict thread matches above, loose matches on Subject: below --
2025-01-14 16:17 Arulpandiyan Vadivel
2025-01-15 3:20 ` Paul Moore
2025-02-27 0:17 ` Paul Moore
2025-02-28 19:42 ` Kees Cook
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=2025011322-climatic-rotting-5b03@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arulpandiyan.vadivel@siemens.com \
--cc=cedric.hombourger@siemens.com \
--cc=linux-modules@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=srikanth.krishnakar@siemens.com \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).