From: Jonathan Corbet <corbet@lwn.net>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Linux Security Module list
<linux-security-module@vger.kernel.org>,
linux-doc@vger.kernel.org, James Morris <jmorris@namei.org>
Subject: Re: [PATCH RFC] Documentation: LSM: Correct the basic LSM description
Date: Tue, 21 Apr 2020 09:17:49 -0600 [thread overview]
Message-ID: <20200421091749.20594692@lwn.net> (raw)
In-Reply-To: <3d5970b8-f95a-2f15-851a-472cbceb94d4@schaufler-ca.com>
On Mon, 20 Apr 2020 17:02:41 -0700
Casey Schaufler <casey@schaufler-ca.com> wrote:
> This is a first pass at updating the basic documentation on
> Linux Security Modules (LSM), which is frighteningly out of date.
> Remove untrue statements about the LSM framework. Replace them
> with true statements where it is convenient to do so. This is
> the beginning of a larger effort to bring the LSM documentation
> up to date.
Seems like a good set of changes overall. One small nit...
> +The LSM framework provides for a close approximation of
> +general security module stacking. It defines
> +:c:func:`security_add_hooks()` to which each security module passes a
> +:c:type:`struct security_hooks_list <security_hooks_list>`,
> +which are added to the lists.
> +The LSM framework does not provide a mechanism for removing hooks that
> +have been registered. An individual security module chose to implement
> +such a mechanism, but the safety of such a mechanism is in no way
> +guaranteed by the framework.
There is no need for :c:func: anymore; just say security_add_hooks() and
the Right Thing™ will happen. It would be good to take all of those out
while you're thrashing up the file.
I really need to get back and do the same thing for :c:type: ...
Thanks,
jon
next prev parent reply other threads:[~2020-04-21 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3d5970b8-f95a-2f15-851a-472cbceb94d4.ref@schaufler-ca.com>
2020-04-21 0:02 ` [PATCH RFC] Documentation: LSM: Correct the basic LSM description Casey Schaufler
2020-04-21 15:17 ` Jonathan Corbet [this message]
2020-04-21 16:17 ` Randy Dunlap
2020-04-23 0:14 ` James Morris
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=20200421091749.20594692@lwn.net \
--to=corbet@lwn.net \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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 NNTP newsgroup(s).