From: Randy Dunlap <rdunlap@infradead.org>
To: Casey Schaufler <casey@schaufler-ca.com>,
Linux Security Summit Program Committee
<lss-pc@lists.linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Cc: James Morris <jmorris@namei.org>
Subject: Re: [PATCH] Documentation: LSM: Correct the basic LSM description
Date: Tue, 21 Apr 2020 14:55:13 -0700 [thread overview]
Message-ID: <0efe8670-cbd7-9633-dbd3-ad04272e6806@infradead.org> (raw)
In-Reply-To: <4c053d72-2d58-612f-6d6b-f04226d0181e@schaufler-ca.com>
On 4/21/20 2:48 PM, Casey Schaufler 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 beginnig of a larger effort to bring the LSM documentation
> up to date.
>
> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
LGTM. Thanks.
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Documentation/security/lsm.rst | 202 ++++++++++++++---------------------------
> 1 file changed, 66 insertions(+), 136 deletions(-)
--
~Randy
next prev parent reply other threads:[~2020-04-21 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4c053d72-2d58-612f-6d6b-f04226d0181e.ref@schaufler-ca.com>
2020-04-21 21:48 ` [PATCH] Documentation: LSM: Correct the basic LSM description Casey Schaufler
2020-04-21 21:54 ` [lss-pc] " Casey Schaufler
2020-04-21 21:55 ` Randy Dunlap [this message]
2020-04-28 18:44 ` Jonathan Corbet
2020-04-29 7:03 ` 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=0efe8670-cbd7-9633-dbd3-ad04272e6806@infradead.org \
--to=rdunlap@infradead.org \
--cc=casey@schaufler-ca.com \
--cc=corbet@lwn.net \
--cc=jmorris@namei.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lss-pc@lists.linuxfoundation.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).