public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: Andrew Morton <akpm@digeo.com>
Cc: gj@pointblue.com.pl, torvalds@transmeta.com,
	linux-kernel@vger.kernel.org, linux-security-module@wirex.com,
	greg@kroah.com, sds@epoch.ncsc.mil
Subject: Re: [PATCH][LSM] Early init for security modules and various cleanups
Date: Mon, 2 Jun 2003 09:33:57 -0700	[thread overview]
Message-ID: <20030602093356.K27233@figure1.int.wirex.com> (raw)
In-Reply-To: <20030602034419.3776d3b7.akpm@digeo.com>; from akpm@digeo.com on Mon, Jun 02, 2003 at 03:44:19AM -0700

* Andrew Morton (akpm@digeo.com) wrote:
> Chris Wright <chris@wirex.com> wrote:
> >
> > security_capable() returns 0 if that capability bit is set. 
> 
> That's just bizarre.  Is there any logic behind it?

Yes, as Stephen pointed out, it's common for the security interface to
return 0 on success on -errno on failure.

cheers,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

      parent reply	other threads:[~2003-06-02 16:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02  9:49 [BK PATCH][LSM] Early init for security modules and various cleanups Chris Wright
2003-06-02  9:54 ` [PATCH][LSM] " Chris Wright
2003-06-02  9:57   ` Chris Wright
2003-06-02 10:00     ` Chris Wright
2003-06-02 10:01       ` Chris Wright
2003-06-02 10:03         ` Chris Wright
2003-06-02 10:08   ` Grzegorz Jaskiewicz
2003-06-02 10:09     ` Chris Wright
2003-06-02 10:44       ` Andrew Morton
2003-06-02 12:50         ` Stephen Smalley
2003-06-02 14:40           ` Chris Friesen
2003-06-02 16:33         ` Chris Wright [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=20030602093356.K27233@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=akpm@digeo.com \
    --cc=gj@pointblue.com.pl \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.com \
    --cc=sds@epoch.ncsc.mil \
    --cc=torvalds@transmeta.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