From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Arne Wiebalck <arne.wiebalck@cern.ch>
Cc: linux-scsi@vger.kernel.org
Subject: RE: SG_IO permissions
Date: Thu, 03 Jul 2008 10:06:30 -0500 [thread overview]
Message-ID: <1215097591.3309.1.camel@localhost.localdomain> (raw)
In-Reply-To: <1215076505.5058.146.camel@pcitfio23.cern.ch>
On Thu, 2008-07-03 at 11:15 +0200, Arne Wiebalck wrote:
> > > >Should the user process get CAP_SYS_RAWIO?
> > >
> > > The user process in my case is forked by another process which runs
> > > as root. But since this process does not have CAP_SETPCAP it cannot
> > > set the child's capabilities (which is how I naively thought one could
> > > implement this).
> > >
> > > What options are left? Running a patched kernel where the "SG_IO in st
> > > requires CAP_SYS_RAWIO" is taken out?
> >
> > Erm, well capabilities are designed to be malleable, especially with
> > things like sucap and execap, which root should be able to use.
>
> But you need to change and recompile your kernel to use that, as init
> needs CAP_SETPCAP to be set, no?
Well .. how you do that isn't really a SCSI problem. The FAQ has one
solution. I suppose rebuilding your kernel is another possible but
inelegant one.
James
next prev parent reply other threads:[~2008-07-03 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 13:20 SG_IO permissions Arne Wiebalck
2008-07-02 14:51 ` James Bottomley
2008-07-02 18:00 ` Arne Wiebalck
2008-07-02 18:40 ` Arne Wiebalck
2008-07-02 20:28 ` James Bottomley
2008-07-03 9:15 ` Arne Wiebalck
2008-07-03 15:06 ` James Bottomley [this message]
2008-07-03 17:57 ` KELEMEN Peter
2008-07-04 8:13 ` Arne Wiebalck
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=1215097591.3309.1.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=arne.wiebalck@cern.ch \
--cc=linux-scsi@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 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.