All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: tabris <tabris@tabris.net>
Cc: linux-kernel@vger.kernel.org,
	"Alexander E. Patrakov" <patrakov@ums.usu.ru>
Subject: Re: ide-cd problems
Date: Mon, 2 Aug 2004 15:56:16 +0200	[thread overview]
Message-ID: <20040802135615.GX10496@suse.de> (raw)
In-Reply-To: <200408020945.05297.tabris@tabris.net>

On Mon, Aug 02 2004, tabris wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sunday 01 August 2004 11:57 am, Jens Axboe wrote:
> > On Sun, Aug 01 2004, Alexander E. Patrakov wrote:
> > > Zinx Verituse wrote:
> > > >I don't believe command filtering is neccessary, since all of the
> > > >ide-cd ioctls are still there (ioctls that allow playing, reading,
> > > > etc) Only the SG_IO ioctl itself would have to be checked (i.e.,
> > > > not each individual command available with SG_IO, just the
> > > > overall ioctl itself, categorizing all of SG_IO more or less as
> > > > raw IO.  If this isn't doable with the current design, then the
> > > > ide-cd interface should at least be very conspicuously documented
> > > > as being extremely insecure as far as "read" access is concerned,
> > > > as I know I wouldn't expect users to be able to overwrite my
> > > > drive's firmware simply by granting the read access.
> > >
> > > Remember that it is still possible to write CDs through ide-cd in
> > > 2.4.x using some pre-alpha code in cdrecord:
> > >
> > > cdrecord dev=ATAPI:1,1,0 image.iso
> >
> > (don't trim cc lists on linux-kernel!)
> >
> > Don't ever use that interface, period. It's not just the cdrecord
> > code that may be alpha (I doubt it matters, it's easy to use), the
> > interface it uses is not worth the lines of code it occupies.
> 	Then we have a severe disagreement between the cdrecord code (or at 
> least the runtime warnings) and the Linux-Kernel IDE folks. 
> specifically, these lines, while running with cdrecord dev=/dev/cdrom
> 
> scsidev: '/dev/cdrom'
> devname: '/dev/cdrom'
> scsibus: -2 target: -2 lun: -2
> Warning: Open by 'devname' is unintentional and not supported.

Kernel and cdrecord disagreement, news at 11.

> 	I've attached two logs, one using the ATAPI interface, one using
> 	your suggested interface. Frankly, both have rather nasty
> 	warnings on them, and one gets to wondering what the cdrecord
> 	authors want...
> 
> 	Maybe we should be cc:ing the authors of cdrecord as well?

I appreciate the good intentions, but perhaps you should research a bit
of background on this before going over board here. Don't think it
hasn't been suggested to Joerg before to kill that message.

Look at the errors as well - one is about the transport used:

> devname: 'ATAPI'
> scsibus: 0 target: 0 lun: 0
> Warning: Using ATA Packet interface.
> Warning: The related libscg interface code is in pre alpha.
> Warning: There may be fatal problems.
> SCSI buffer size: 64512

The other (for SG_IO)

> scsidev: '/dev/cdrom'
> devname: '/dev/cdrom'
> scsibus: -2 target: -2 lun: -2
> Warning: Open by 'devname' is unintentional and not supported.

just says that open-by-device name is unintentional, it doesn't give you
warnings on the transport.

So in short (and repeating): don't use ATAPI (CDROM_SEND_PACKET), it
sucks. Use SG_IO (which means using open-by-device, which works at least
as well as the stupid faked ATAPI bus/id/lun crap and has the much
better transport). Don't compare apples and oranges.

-- 
Jens Axboe


  reply	other threads:[~2004-08-02 13:57 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 19:36 ide-cd problems Zinx Verituse
2004-07-31 15:36 ` Jens Axboe
2004-07-31 18:27   ` Zinx Verituse
2004-07-31 20:00     ` Jens Axboe
2004-07-31 21:02       ` Zinx Verituse
2004-08-01  4:07         ` Alexander E. Patrakov
2004-08-01 15:57           ` Jens Axboe
2004-08-02  3:20             ` Horst von Brand
2004-08-02 12:25               ` Jens Axboe
2004-08-02 20:44               ` Bill Davidsen
2004-08-02 13:45             ` tabris
2004-08-02 13:56               ` Jens Axboe [this message]
2004-08-02 14:26                 ` Andreas Metzler
2004-08-02 14:33                   ` Jens Axboe
2004-08-02 14:38                 ` tabris
2004-08-02 14:50                   ` Jens Axboe
2004-08-02 16:30           ` Bill Davidsen
2004-08-03  7:17             ` Jens Axboe
2004-08-02 17:16         ` Zinx Verituse
2004-08-05  5:40         ` Jens Axboe
2004-08-05 21:06           ` Alan Cox
2004-08-06  5:44             ` Jens Axboe
     [not found]               ` <20040806062331.GE10274@suse.de>
2004-08-06 12:14                 ` Alan Cox
2004-08-06 14:32                   ` Jens Axboe
2004-08-06 15:14                     ` Charles Cazabon
2004-08-06 15:13                       ` Jens Axboe
2004-08-07 14:01                       ` Alan Cox
2004-08-06 17:26                     ` dleonard
2004-08-06 22:47                       ` Jens Axboe
2004-08-07 14:04                         ` Alan Cox
2004-08-07 21:54                           ` Alan Cox
2004-08-07  3:11                     ` Jason L Tibbitts III
2004-08-09  8:39                       ` Jens Axboe
2004-08-07 14:08                     ` Alan Cox
2004-08-09  8:49                       ` Jens Axboe
2004-08-02 23:54       ` Alan Cox
2004-08-03  5:53         ` Jens Axboe
2004-08-03 16:17           ` Zinx Verituse
2004-08-04  5:01             ` Jens Axboe
2004-08-05 15:52               ` Alan Cox
2004-08-05 17:46                 ` Jens Axboe
2004-08-05 20:58                   ` Alan Cox
2004-08-05 18:53                 ` Bill Davidsen
2004-08-05 18:46           ` Bill Davidsen
2004-08-05 19:35             ` Jens Axboe
2004-08-05 21:02               ` Alan Cox
2004-08-06  5:42                 ` Jens Axboe
2004-08-03 15:28         ` Doug Maxey
2004-08-03 17:28           ` Alan Cox
2004-08-09 20:24       ` Bill Davidsen
2004-08-02 16:41   ` Bill Davidsen
2004-08-03 15:50     ` Horst von Brand

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=20040802135615.GX10496@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrakov@ums.usu.ru \
    --cc=tabris@tabris.net \
    /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.