mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mathieu Fluhr <mfluhr@nero.com>
To: linux-kernel@vger.kernel.org
Subject: Vendor specific SCSI opcodes
Date: Mon, 15 Aug 2005 15:34:08 +0200	[thread overview]
Message-ID: <1124112848.1945.14.camel@localhost.localdomain> (raw)

Hello all

I have a problem when using vendor-specific SCSI opcodes with the
ide-cdrom drive. Unless I run the CDROM_SEND_PACKET ioctl as root, I am
getting an error.... plus a kernel warning: 
  Aug 10 12:09:08 localhost kernel: scsi: unknown opcode 0xfa

(..and there is not only 0xfa ad opcode ;-)

As far as I have understood the kernel source code, the problem seems to
be related to the verify_command() introduced in 2.6.8. The thing is
that all these vendor-specific opcodes are not inside the 'cmd_type',
and so not 'safe'.
Nice thing is that when I use exactly the same device over an IDE-to-USB
bridge, it is working like a charm ;-)

So is there a way to bypass this command verification and to let the
program work without launching it as root user ?

Best Regards,
Mathieu



             reply	other threads:[~2005-08-15 13:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 13:34 Mathieu Fluhr [this message]
2005-08-15 14:42 ` Alan Cox

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=1124112848.1945.14.camel@localhost.localdomain \
    --to=mfluhr@nero.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
Powered by JetHome