[PATCH] security: fix LSM description location

[PATCH] security: fix LSM description location

[Randy Dunlap]

From: Randy Dunlap <rdunlap@infradead.org>

Fix Documentation location reference for where LSM descriptions should
be placed.

Suggested-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: James Morris <jmorris@namei.org>
Cc: "Serge E. Hallyn" <serge@hallyn.com>
Cc: linux-security-module@vger.kernel.org
---
 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.

Re: [PATCH] security: fix LSM description location

[Kees Cook]

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

Thanks!

Acked-by: Kees Cook <keescook@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

Re: [PATCH] security: fix LSM description location

[James Morris]

On Mon, 8 Oct 2018, Randy Dunlap wrote:

> From: Randy Dunlap <rdunlap@infradead.org>
> 
> Fix Documentation location reference for where LSM descriptions should
> be placed.
> 
> Suggested-by: Kees Cook <keescook@chromium.org>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: James Morris <jmorris@namei.org>
> Cc: "Serge E. Hallyn" <serge@hallyn.com>
> Cc: linux-security-module@vger.kernel.org

Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general

-- 
James Morris
<jmorris@namei.org>