All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: akpm@osdl.org, linux-scsi@vger.kernel.org, T.Maguin@web.de
Subject: Re: [patch 23/28] scsi cd: VariRec, GigaRec and PowerRec as user
Date: Wed, 8 Mar 2006 16:15:35 +0100	[thread overview]
Message-ID: <20060308151535.GU4595@suse.de> (raw)
In-Reply-To: <1141830726.3194.8.camel@mulgrave.il.steeleye.com>

On Wed, Mar 08 2006, James Bottomley wrote:
> On Wed, 2006-03-08 at 00:14 -0800, akpm@osdl.org wrote:
> > From: Thomas Maguin <T.Maguin@web.de>
> 
> > This patch allows normal users to eectute some Plextor drives
> > commands:
> > 
> > - Hide CD-R
> > - SingleSession
> > - SpeedRead
> > - PowerRec
> > - VariRec
> > - GigaRec
> > 
> 
> This one just isn't safe.  We can't add vendor specific commands to the
> permissions table because they mean different things to different
> vendors ... get mode on one could be halt and catch fire on another, so
> the whole concept of safety via command verification is lost.
> 
> I don't happen to believe in this type of command verification anyway,
> so I'd be perfectly happy to switch this over to a better facility (like
> capabilities), but while you're claiming to vet commands, you have to be
> logically correct (which means no vendor specific commands).

I have to agree, unfortunately... Perhaps this is some motivation to get
the fs permission table into the mainline kernel for 2.6.17. It's the
'cmdfilter' branch of the git block repo. Then we could finally get rid
of this ugly command table.

-- 
Jens Axboe


  reply	other threads:[~2006-03-08 15:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200603080816.k288GSQO002236@shell0.pdx.osdl.net>
2006-03-08 15:12 ` [patch 23/28] scsi cd: VariRec, GigaRec and PowerRec as user James Bottomley
2006-03-08 15:15   ` Jens Axboe [this message]
2006-03-08 15:45   ` Matthew Wilcox
2006-03-08 17:30     ` Jeff Garzik

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=20060308151535.GU4595@suse.de \
    --to=axboe@suse.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=T.Maguin@web.de \
    --cc=akpm@osdl.org \
    --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.