From: Chris Wright <chris@wirex.com>
To: Tony Glader <Tony.Glader@blueberrysolutions.com>
Cc: Chris Wright <chris@wirex.com>, linux-kernel@vger.kernel.org
Subject: Re: capable()-function
Date: Wed, 9 Oct 2002 12:08:19 -0700 [thread overview]
Message-ID: <20021009120819.A25392@figure1.int.wirex.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210092135240.411-100000@blueberrysolutions.com>; from Tony.Glader@blueberrysolutions.com on Wed, Oct 09, 2002 at 09:39:18PM +0300
* Tony Glader (Tony.Glader@blueberrysolutions.com) wrote:
> On Wed, 9 Oct 2002, Chris Wright wrote:
>
> > > I was investigating problems with PCMCIA and found that
> > > capable(CAP_SYS_ADMIN) returns always false in my case. If I'm calling
> > Typically root has all effective capabilities (except CAP_SETPCAP).
> > You can check your effective capabilities in /proc/[pid]/status.
>
> In this case capable() call has been made from a kernel module. I think a
> module doesn't have a PID? Should I check capabilites of program that does
> a ioctl() call that will cause module to do capable() checking?
The userspace task that called the ioctl() is the one to look at.
> Process that does ioctl() call is owned by root and has following
> capabilities:
>
> CapInh: 0000000000000000
> CapPrm: 00000000fffffeff
> CapEff: 00000000fffffeff
Ok, I don't think the capable() check is failing.
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2002-10-09 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 7:51 capable()-function Tony Glader
2002-10-09 18:22 ` capable()-function Chris Wright
2002-10-09 18:39 ` capable()-function Tony Glader
2002-10-09 19:08 ` Chris Wright [this message]
2002-10-09 19:19 ` capable()-function Tony Glader
2002-10-09 19:16 ` capable()-function Chris Wright
2002-10-09 20:16 ` capable()-function Tony Glader
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=20021009120819.A25392@figure1.int.wirex.com \
--to=chris@wirex.com \
--cc=Tony.Glader@blueberrysolutions.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®