[PATCH] security: fix LSM description location

Kees Cook keescook at chromium.org
Tue Oct 9 01:40:08 UTC 2018


On Mon, Oct 8, 2018 at 5:46 PM, Randy Dunlap <rdunlap at infradead.org> wrote:
> From: Randy Dunlap <rdunlap at infradead.org>
>
> Fix Documentation location reference for where LSM descriptions should
> be placed.
>
> Suggested-by: Kees Cook <keescook at chromium.org>
> Signed-off-by: Randy Dunlap <rdunlap at infradead.org>
> Cc: James Morris <jmorris at namei.org>
> Cc: "Serge E. Hallyn" <serge at hallyn.com>
> Cc: linux-security-module at vger.kernel.org

Thanks!

Acked-by: Kees Cook <keescook at chromium.org>

Jon, can you take this?

-Kees

> ---
>  Documentation/security/LSM.rst |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- lnx-419-rc7.orig/Documentation/security/LSM.rst
> +++ lnx-419-rc7/Documentation/security/LSM.rst
> @@ -5,7 +5,7 @@ Linux Security Module Development
>  Based on https://lkml.org/lkml/2007/10/26/215,
>  a new LSM is accepted into the kernel when its intent (a description of
>  what it tries to protect against and in what cases one would expect to
> -use it) has been appropriately documented in ``Documentation/security/LSM.rst``.
> +use it) has been appropriately documented in ``Documentation/admin-guide/LSM/``.
>  This allows an LSM's code to be easily compared to its goals, and so
>  that end users and distros can make a more informed decision about which
>  LSMs suit their requirements.
>
>



-- 
Kees Cook
Pixel Security



More information about the Linux-security-module-archive mailing list