From: Casey Schaufler <casey@schaufler-ca.com>
To: Andrew Morton <akpm@linux-foundation.org>, casey@schaufler-ca.com
Cc: torvalds@linux-foundation.org, morgan@kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] -mm (2.4.26-rc3-mm1) v2 Smack using capabilities 32 and 33
Date: Tue, 27 Nov 2007 13:48:17 -0800 (PST) [thread overview]
Message-ID: <611606.13033.qm@web36606.mail.mud.yahoo.com> (raw)
In-Reply-To: <20071127131632.808bf9f8.akpm@linux-foundation.org>
--- Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > + !__capable(current, CAP_MAC_ADMIN))
> > + !__capable(current, CAP_MAC_ADMIN))
>
> Is there any reason for not using plain old capable() here?
Nope. I'll clean that up.
Thank you.
Casey Schaufler
casey@schaufler-ca.com
prev parent reply other threads:[~2007-11-27 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 20:38 [PATCH] -mm (2.4.26-rc3-mm1) v2 Smack using capabilities 32 and 33 Casey Schaufler
2007-11-26 21:36 ` Serge E. Hallyn
2007-11-27 3:22 ` Andrew Morgan
2007-11-27 21:16 ` Andrew Morton
2007-11-27 21:48 ` 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=611606.13033.qm@web36606.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=torvalds@linux-foundation.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