All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Paul Moore <paul@paul-moore.com>
Cc: serge@hallyn.com, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] capability: Remove unused has_capability
Date: Thu, 19 Dec 2024 17:29:52 +0000	[thread overview]
Message-ID: <Z2RYECe3OIS4Hcl4@gallifrey> (raw)
In-Reply-To: <CAHC9VhTZ98OwAAtk52MreZaU1OJwKS6PqOU=SCzhfBYNEM8qqw@mail.gmail.com>

* Paul Moore (paul@paul-moore.com) wrote:
> On Thu, Dec 19, 2024 at 9:19 AM Dr. David Alan Gilbert
> <linux@treblig.org> wrote:
> >
> > OK, maybe:
> >
> > * NOTE WELL: cap_capable() has reverse semantics to the capable() call
> > * and friends. That is cap_capable() returns an int 0 when a task has
> > * a capability, while the kernel's capable(), has_ns_capability(),
> > * has_ns_capability_noaudit(), and has_capability_noaudit() return a
> > * bool true (1) for this case.
> 
> Works for me, thanks.

Thanks,

v2 sent - see 20241219172859.188117-1-linux@treblig.org

Dave

> -- 
> paul-moore.com
> 
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\        dave @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

      reply	other threads:[~2024-12-19 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-15 16:53 [PATCH] capability: Remove unused has_capability linux
2024-12-18 21:31 ` Paul Moore
2024-12-18 22:11   ` Dr. David Alan Gilbert
2024-12-19  2:24     ` Paul Moore
2024-12-19 14:19       ` Dr. David Alan Gilbert
2024-12-19 14:55         ` Paul Moore
2024-12-19 17:29           ` Dr. David Alan Gilbert [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=Z2RYECe3OIS4Hcl4@gallifrey \
    --to=linux@treblig.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=serge@hallyn.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 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.