security: fix LSM description location
authorRandy Dunlap <rdunlap@infradead.org>
Tue, 9 Oct 2018 00:46:04 +0000 (17:46 -0700)
committerJames Morris <james.morris@microsoft.com>
Tue, 9 Oct 2018 19:18:38 +0000 (12:18 -0700)
Acked-by: Kees Cook <keescook@chromium.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
Signed-off-by: James Morris <james.morris@microsoft.com>
Documentation/security/LSM.rst

index 98522e0e1ee23278f8ffbe2aa4b6ad1a46e09f1e..8b9ee597e9d0ec02bb7555eca34dbac9e306e518 100644 (file)
@@ -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.