public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Daniel Drake <dsd@gentoo.org>
Cc: "Alexander E. Patrakov" <patrakov@ums.usu.ru>,
	linux-kernel@vger.kernel.org
Subject: Re: Missing SCSI command in the allowed list?
Date: Thu, 18 Nov 2004 19:40:39 +0100	[thread overview]
Message-ID: <20041118184039.GM26240@suse.de> (raw)
In-Reply-To: <419CEC65.4020603@gentoo.org>

On Thu, Nov 18 2004, Daniel Drake wrote:
> Hi,
> 
> Alexander E. Patrakov wrote:
> >But the question remains: what should the users of not 100% MMC-compatible
> >CR-RW drives (i.e. those which have a separate cdrado or cdrecord driver,
> >not generic-mmc/generic-mmc-raw) do? Is the support for writing as non-root
> >on such drives just dropped without any plans to "fix" it?
> 
> I'd also be interested to know the answer here. Jens?
> 
> Some Gentoo users have reported that commands such as ED/EB/E9/F5 are being 
> rejected. When inspecting the cdrecord source code, it seems that these are 
> specific to plextor drives. These drives are MMC but have a few 
> vendor-specific extensions. How should we go about permitting cases like 
> this in the command filter?

See Alans post, that's the only real way to deal with the situation.
Right now we are stuck with half a solution (which is better than none
or the 5% initial solution), it would still be nice to have it finished.
Search the archives, there were several posts on this.

-- 
Jens Axboe


      parent reply	other threads:[~2004-11-18 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06 13:47 Missing SCSI command in the allowed list? Alexander E. Patrakov
2004-11-06 16:24 ` Daniel Drake
2004-11-07  7:56   ` Alexander E. Patrakov
2004-11-18 18:39     ` Daniel Drake
2004-11-18 16:23       ` Alan Cox
2004-11-18 18:40       ` Jens Axboe [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=20041118184039.GM26240@suse.de \
    --to=axboe@suse.de \
    --cc=dsd@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrakov@ums.usu.ru \
    /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