From: James Morris <jmorris@namei.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] Documentation: LSM: Correct the basic LSM description
Date: Wed, 29 Apr 2020 17:03:24 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.2004291700110.19446@namei.org> (raw)
In-Reply-To: <20200428124436.1c7463ee@lwn.net>
On Tue, 28 Apr 2020, Jonathan Corbet wrote:
> On Tue, 21 Apr 2020 14:48:34 -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 beginnig of a larger effort to bring the LSM documentation
> > up to date.
> >
> > Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
> > ---
> > Documentation/security/lsm.rst | 202 ++++++++++++++---------------------------
> > 1 file changed, 66 insertions(+), 136 deletions(-)
>
> James, are you planning to pick this up, or should I grab it?
You can grab it, but I don't think this patch ended up on the lsm list for
review (I only caught it in the moderation queue for lss-pc).
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2020-04-29 7:03 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 ` Casey Schaufler
2020-04-21 21:54 ` [lss-pc] " Casey Schaufler
2020-04-21 21:55 ` Randy Dunlap
2020-04-28 18:44 ` Jonathan Corbet
2020-04-29 7:03 ` James Morris [this message]
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=alpine.LRH.2.21.2004291700110.19446@namei.org \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®