public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Thomas Fritzsche <tf@noto.de>
Cc: Pasi Savolainen <psavo@iki.fi>, linux-kernel@vger.kernel.org
Subject: Re: Is controlling DVD speeds via SET_STREAMING supported?
Date: Sun, 28 Nov 2004 17:52:58 +0100	[thread overview]
Message-ID: <20041128165257.GA26714@suse.de> (raw)
In-Reply-To: <33050.192.168.0.5.1101651929.squirrel@192.168.0.10>

On Sun, Nov 28 2004, Thomas Fritzsche wrote:
> Hi,
> 
> (please CC me because I'm not subscribed to the list)
> 
> >> What Kernel do you use?
> >
> > Linux tienel 2.6.10-rc2-mm1 #1 SMP Wed Nov 17 01:19:53 EET 2004 i686
> > GNU/Linux
> 
> Maybe you can give a 2.4.27'er kernel a try.
> 
> >
> > Actually now that I rebooted (for DVD flashing) and started back into
> > linux, after running dvdspeed it also says:
> > "scsi: unknown opcode 0xb6" (which is SET_STREAMING). Code for this is
> > in drivers/block/scsi_ioctl.c, and if I read it right, it can't prevent
> > root from executing that command.
> 
> I have the same impression after reading drivers/block/scsi_ioctl.c . I
> think you will need root permission to send this command, RW-Permission
> for the device file is not enough! Did you try this as root?

You just need to add SET_STREAMINIG as a write-safe command, then it
will work as a regular user. Hmm, it is already added as write safe. You
don't have write permission on the device, then.

> But I'm wondering that scsi_ioctl.c comes into play, because It's a
> ATAPI-Device. Isn't it? Do you use the scsi emulation? If so please try
> without.

The 'scsi' in the name doesn't refer to the transport used, but the
command set being scsi-like. ide-scsi emulation has nothing to do with
it.

> > I modified your speed-1.0 to open device O_RDWR, didn't help.
> > I modified it to also dump_sense after CMD_SEND_PACKET, it's just
> > duplicate packet.
> 
> No this will definitively not solve this issue. I will try to check this
> in the kernel, but because I'm not a kernel developer I will CC Jens
> Axboe. Maybe he can help?

Just fix the permission on the special file. Additionally, the program
must open the device O_RDWR.

-- 
Jens Axboe


  reply	other threads:[~2004-11-28 16:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-26 19:59 Re: Is controlling DVD speeds via SET_STREAMING supported? Thomas Fritzsche
2004-11-27  9:54 ` Thomas Fritzsche
2004-11-27 20:57   ` Pasi Savolainen
2004-11-27 21:02     ` Jan Engelhardt
2004-11-27 23:17     ` Thomas Fritzsche
2004-11-28 11:18       ` Pasi Savolainen
2004-11-28 14:25         ` Thomas Fritzsche
2004-11-28 16:52           ` Jens Axboe [this message]
2004-11-28 17:49             ` Pasi Savolainen
2004-11-28 16:53               ` Thomas Fritzsche
2004-11-28 18:53               ` Jens Axboe
2004-11-28 21:01                 ` Pasi Savolainen
2004-11-29  6:19                   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2004-11-20 16:17 David Härdeman
2004-11-20 16:30 ` Jan Engelhardt
2004-11-20 16:45   ` David Härdeman
2004-11-20 20:19 ` Jens Axboe
2004-11-20 23:50   ` David Härdeman

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=20041128165257.GA26714@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psavo@iki.fi \
    --cc=tf@noto.de \
    /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