From: james.l.morris@oracle.com (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [RFC v2 1/3] security: Add safe, dynamic (runtime-loadable) hook support
Date: Mon, 11 Dec 2017 09:28:20 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1712110923210.19397@localhost> (raw)
In-Reply-To: <5c089f6eb3bcec36e6021db7dcfcd4409be99111.1512704909.git.sargun@netflix.com>
On Fri, 8 Dec 2017, Sargun Dhillon wrote:
> The primary purpose of this patchset is to facilitate the development of
> out-of-tree minor LSMs.
This is not a valid use-case for the mainline kernel: we don't add
features for out of tree code.
Please reconsider your rationale :-)
- James
--
James Morris
<james.l.morris@oracle.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <james.l.morris@oracle.com>
To: Sargun Dhillon <sargun@sargun.me>
Cc: linux-security-module@vger.kernel.org, keescook@chromium.org,
igor.stoppa@huawei.com, casey@schaufler-ca.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC v2 1/3] security: Add safe, dynamic (runtime-loadable) hook support
Date: Mon, 11 Dec 2017 09:28:20 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1712110923210.19397@localhost> (raw)
In-Reply-To: <5c089f6eb3bcec36e6021db7dcfcd4409be99111.1512704909.git.sargun@netflix.com>
On Fri, 8 Dec 2017, Sargun Dhillon wrote:
> The primary purpose of this patchset is to facilitate the development of
> out-of-tree minor LSMs.
This is not a valid use-case for the mainline kernel: we don't add
features for out of tree code.
Please reconsider your rationale :-)
- James
--
James Morris
<james.l.morris@oracle.com>
next prev parent reply other threads:[~2017-12-10 22:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1512704909.git.sargun@netflix.com>
2017-12-08 4:24 ` [RFC v2 1/3] security: Add safe, dynamic (runtime-loadable) hook support Sargun Dhillon
2017-12-08 4:24 ` Sargun Dhillon
2017-12-08 16:27 ` Casey Schaufler
2017-12-08 16:27 ` Casey Schaufler
2017-12-10 22:10 ` James Morris
2017-12-10 22:10 ` James Morris
2017-12-11 10:22 ` Tetsuo Handa
2017-12-11 10:22 ` Tetsuo Handa
2017-12-10 22:28 ` James Morris [this message]
2017-12-10 22:28 ` James Morris
2017-12-13 12:38 ` Sargun Dhillon
2017-12-13 12:38 ` Sargun Dhillon
2017-12-08 4:24 ` [RFC v2 2/3] LSM: Add statistics about the invocation of dynamic hooks Sargun Dhillon
2017-12-08 4:24 ` Sargun Dhillon
2017-12-08 16:31 ` Casey Schaufler
2017-12-08 16:31 ` Casey Schaufler
2017-12-10 22:21 ` James Morris
2017-12-10 22:21 ` James Morris
2017-12-08 4:24 ` [RFC v2 3/3] LSM: Add an example sample dynamic LSM Sargun Dhillon
2017-12-08 4:24 ` Sargun Dhillon
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.LFD.2.20.1712110923210.19397@localhost \
--to=james.l.morris@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.