From: Kees Cook <keescook@chromium.org>
To: Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E . Hallyn" <serge@hallyn.com>,
Stephen Boyd <swboyd@chromium.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, patches@lists.linux.dev,
linux-security-module@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH] loadpin: Prevent SECURITY_LOADPIN_ENFORCE=y without module decompression
Date: Tue, 14 May 2024 15:52:13 -0700 [thread overview]
Message-ID: <171572713190.2793228.3146950773342970247.b4-ty@chromium.org> (raw)
In-Reply-To: <20240514224839.2526112-1-swboyd@chromium.org>
On Tue, 14 May 2024 15:48:38 -0700, Stephen Boyd wrote:
> If modules are built compressed, and LoadPin is enforcing by default, we
> must have in-kernel module decompression enabled (MODULE_DECOMPRESS).
> Modules will fail to load without decompression built into the kernel
> because they'll be blocked by LoadPin. Add a depends on clause to
> prevent this combination.
>
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] loadpin: Prevent SECURITY_LOADPIN_ENFORCE=y without module decompression
https://git.kernel.org/kees/c/bc9316c14441
Take care,
--
Kees Cook
next prev parent reply other threads:[~2024-05-14 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 22:48 [PATCH] loadpin: Prevent SECURITY_LOADPIN_ENFORCE=y without module decompression Stephen Boyd
2024-05-14 22:52 ` Kees Cook [this message]
2024-05-18 20:47 ` Kees Cook
2024-05-21 4:14 ` Stephen Boyd
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=171572713190.2793228.3146950773342970247.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=swboyd@chromium.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 read-only IMAP folder(s) and NNTP newsgroup(s).