From: Casey Schaufler <casey@schaufler-ca.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Eric Paris <eparis@redhat.com>, Don Dutile <ddutile@redhat.com>,
James Morris <jmorris@namei.org>,
Serge Hallyn <serge.hallyn@canonical.com>,
linux-security-module@vger.kernel.org,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PATCH 1/2] security: add cred argument to security_capable()
Date: Thu, 10 Feb 2011 08:25:00 -0800 [thread overview]
Message-ID: <4D54115C.6090403@schaufler-ca.com> (raw)
In-Reply-To: <20110210160837.GB9869@sequoia.sous-sol.org>
On 2/10/2011 8:08 AM, Chris Wright wrote:
> * Casey Schaufler (casey@schaufler-ca.com) wrote:
>> On 2/9/2011 10:11 PM, Chris Wright wrote:
>>> Expand security_capable() to include cred, so that it can be usable in a
>>> wider range of call sites.
>> I'll bite. What to plan to use this for? I wouldn't see this getting
>> accepted on its own without a user. I don't see anything wrong with
>> the change other than that it is not used by anything.
> Casey, the user is in 2/2.
Which didn't show up on the LSM list. I see it now, but
had to go looking. Ok, no worries
> https://lkml.org/lkml/2011/2/10/16
>
>
next prev parent reply other threads:[~2011-02-10 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 6:11 [PATCH 0/2] pci: refer to LSM when accessing device dependent config space Chris Wright
2011-02-10 6:11 ` [PATCH 1/2] security: add cred argument to security_capable() Chris Wright
2011-02-10 13:43 ` Serge E. Hallyn
2011-02-10 16:01 ` Casey Schaufler
2011-02-10 16:08 ` Chris Wright
2011-02-10 16:25 ` Casey Schaufler [this message]
2011-02-10 6:11 ` [PATCH 2/2] pci: use security_capable() when checking capablities during config space read Chris Wright
2011-02-10 8:23 ` James Morris
2011-02-10 23:58 ` [PATCH 2/2 v2] " Chris Wright
2011-02-14 17:14 ` Eric Paris
2011-03-04 18:25 ` Jesse Barnes
2011-02-11 7:01 ` [PATCH 0/2] pci: refer to LSM when accessing device dependent config space 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=4D54115C.6090403@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=chrisw@sous-sol.org \
--cc=ddutile@redhat.com \
--cc=eparis@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge.hallyn@canonical.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