diff options
| author | Tom Saeger <tom.saeger@oracle.com> | 2017-10-10 12:36:30 -0500 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2017-10-12 11:14:40 -0600 |
| commit | c7f66400f504fd54bda6ec644853c07333e8cb87 (patch) | |
| tree | 8d7e6e954e0036a297eaf55248ef8e51f18c7340 /Documentation/security/LSM.rst | |
| parent | 1752118d48e7627756acf7fb8c13541305078fed (diff) | |
Documentation: fix security related doc refs
Make security document refs valid.
Signed-off-by: Tom Saeger <tom.saeger@oracle.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/security/LSM.rst')
| -rw-r--r-- | Documentation/security/LSM.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/security/LSM.rst b/Documentation/security/LSM.rst index d75778b0fa10..98522e0e1ee2 100644 --- a/Documentation/security/LSM.rst +++ b/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``. +use it) has been appropriately documented in ``Documentation/security/LSM.rst``. 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. |