From: James Morris <jmorris@namei.org>
To: Paul Moore <paul@paul-moore.com>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
LSM <linux-security-module@vger.kernel.org>
Subject: Re: New LSM hooks
Date: Wed, 6 Feb 2019 12:11:20 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1902061207010.19811@namei.org> (raw)
In-Reply-To: <CAHC9VhQ6p=LoEN6Rqze48FrVDsX0mfXHY4BvEaxU97w1azP4YQ@mail.gmail.com>
On Tue, 5 Feb 2019, Paul Moore wrote:
> I believe that will always be a problem, no matter what we do. The
> point I was trying to make was that everyone, especially the
> maintainers, need to watch for this when patches are posted and make
> sure the patch author posts to the LSM list in addition to any of the
> relevant LSM specific lists.
Right, and there is no way a new LSM hook should ever be added to the
kernel without review and ack/signoffs from folks on the LSM list
(especially those who are maintainers of in-tree LSMs).
Casey, do you have any examples of this happening?
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-02-06 1:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 17:40 New LSM hooks Casey Schaufler
2019-02-05 18:15 ` Paul Moore
2019-02-05 20:04 ` Casey Schaufler
2019-02-06 0:01 ` Paul Moore
2019-02-06 1:11 ` James Morris [this message]
2019-02-06 13:20 ` Stephen Smalley
2019-02-06 17:24 ` Casey Schaufler
2019-02-06 17:44 ` Stephen Smalley
2019-02-06 18:18 ` Casey Schaufler
2019-02-06 16:30 ` Casey Schaufler
2019-02-06 17:06 ` Stephen Smalley
2019-02-06 17:44 ` Casey Schaufler
2019-02-06 17:48 ` Stephen Smalley
2019-02-05 18:28 ` Edwin Zimmerman
2019-02-05 19:25 ` Casey Schaufler
2019-02-05 19:58 ` Paul Moore
2019-02-05 20:10 ` Edwin Zimmerman
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.1902061207010.19811@namei.org \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
/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).