From: Casey Schaufler <casey@schaufler-ca.com>
To: James Morris <jmorris@namei.org>
Cc: LSM <linux-security-module@vger.kernel.org>,
John Johansen <john.johansen@canonical.com>,
Paul Moore <paul@paul-moore.com>,
Kees Cook <keescook@chromium.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
LKLM <linux-kernel@vger.kernel.org>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PATCH] LSM: Add /sys/kernel/security/lsm
Date: Wed, 18 Jan 2017 15:52:42 -0800 [thread overview]
Message-ID: <76235352-9a34-645d-db40-79c2a4a0be63@schaufler-ca.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1701191029020.23247@namei.org>
On 1/18/2017 3:29 PM, James Morris wrote:
> On Tue, 17 Jan 2017, Casey Schaufler wrote:
>
>> Subject: [PATCH] LSM: Add /sys/kernel/security/lsm
>>
>> I am still tired of having to find indirect ways to determine
>> what security modules are active on a system. I have added
>> /sys/kernel/security/lsm, which contains a comma separated
>> list of the active secuirty modules. No more groping around
>> in /proc/filesystems or other clever hacks.
>>
>> Unchanged from previous versions except for being updated
>> to the latest security next branch.
>>
> This doesn't apply cleanly to my tree.
The AppArmor changes that you've added since you pulled
rc3 introduced some offset issues. Should I update my patch
to reflect them, or do you want to resolve the conflict?
I don't much care either way. Just let me know.
prev parent reply other threads:[~2017-01-18 23:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 23:42 Casey Schaufler
2017-01-18 0:25 ` John Johansen
2017-01-18 12:43 ` James Morris
2017-01-18 14:30 ` Tetsuo Handa
2017-01-18 19:22 ` Paul Moore
2017-01-18 21:01 ` Kees Cook
2017-01-18 23:00 ` James Morris
2017-01-18 23:25 ` Casey Schaufler
2017-01-18 23:29 ` James Morris
2017-01-18 23:52 ` Casey Schaufler [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=76235352-9a34-645d-db40-79c2a4a0be63@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sds@tycho.nsa.gov \
/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®