public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Kasper Sandberg <lkml@metanurb.dk>
Cc: Tim Fairchild <tim@bcs4me.com>,
	Alessandro Suardi <alessandro.suardi@gmail.com>,
	Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>,
	LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: DVD burning still have problems
Date: Mon, 24 Jan 2005 18:34:27 +0100	[thread overview]
Message-ID: <20050124173426.GP2707@suse.de> (raw)
In-Reply-To: <1106587560.13336.9.camel@localhost>

On Mon, Jan 24 2005, Kasper Sandberg wrote:
> On Mon, 2005-01-24 at 11:46 +1000, Tim Fairchild wrote:
> > On Monday 24 Jan 2005 06:59, Alessandro Suardi wrote:
> > > On Sun, 23 Jan 2005 21:26:55 +0100, Volker Armin Hemmann
> > >
> > > <volker.armin.hemmann@tu-clausthal.de> wrote:
> > > > Hi,
> > > >
> > > > have you checked, that cdrecord is not suid root, and
> > > > growisofs/dvd+rw-tools is?
> > > >
> > > > I had some probs, solved with a simple chmod +s growisofs :)
> > >
> > > Lucky you. Burning as root here, cdrecord not suid. Tried also
> > >  burning with a +s growisofs, but...
> > 
> > You can test if it's the kernel/growisofs clashing by hacking the
> > drivers/block/scsi_ioctl.c  code
> > 
> > It's around line 193 in 2.6.9, and line 196 in 2.6.10
> > not sure about 2.6.11
> at line 196
> > 
> > find the code:
> > 
> >         /* Write-safe commands just require a writable open.. */
> >         if (type & CMD_WRITE_SAFE) {
> >                 if (file->f_mode & FMODE_WRITE)
> >                         return 0;
> >         }
> > 
> > edit it to something like:
> > 
> >         /* Write-safe commands just require a writable open.. */
> >         if (type & CMD_WRITE_SAFE) {
> >                 printk ("Write safe command in ");
> >                 if (file->f_mode & FMODE_WRITE)
> >                         printk ("write mode.\n");
> >                 else
> >                         printk ("read mode.\n");
> >                 return 0;
> >         }
> > 
> > Compile the kernel with that and that may make it work and burn dvd and let 
> > you know if it's growisofs sending incorrect commands. You'll get messages in 
> > dmesg like
> > 
> > Write safe command in read mode.
> > 
> > which means growisofs is still not right. Maybe later version fixed this?
> i got the latest version, and i just did this, nothing of this appeared
> in dmesg, but also, i dont see what scsi_ioctl has to do with anything?
> i dont use scsi emulation

it doesn't have anything to do with ide-scsi scsi emulation,
direct-to-device SG_IO uses drivers/block/scsi_ioctl.c (note the block/
directory, not scsi/).

strange that it doesn't catch anything...

-- 
Jens Axboe


  reply	other threads:[~2005-01-24 17:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23 20:26 DVD burning still have problems Volker Armin Hemmann
2005-01-23 20:59 ` Alessandro Suardi
2005-01-24  1:46   ` Tim Fairchild
2005-01-24 17:26     ` Kasper Sandberg
2005-01-24 17:34       ` Jens Axboe [this message]
2005-01-24 15:07   ` Jens Axboe
2005-01-24 16:48     ` Alessandro Suardi
2005-01-24 17:21       ` Jens Axboe
2005-01-24 17:24     ` Kasper Sandberg
2005-01-24 17:32       ` Jens Axboe
2005-01-24 19:37     ` Alan Cox
2005-01-24 20:45       ` Jens Axboe
2005-01-24 20:56         ` Alessandro Suardi
2005-01-24 21:44         ` Alan Cox
2005-01-24 23:01           ` Kasper Sandberg
2005-01-24 23:48             ` Alan Cox
2005-01-28 13:42               ` Kasper Sandberg
2005-01-28 13:47                 ` Jens Axboe
2005-01-28 14:05                   ` Kasper Sandberg
2005-01-28 14:45                     ` Kasper Sandberg
2005-01-24 23:02           ` Alessandro Suardi
2005-01-24 23:44             ` Alessandro Suardi
  -- strict thread matches above, loose matches on Subject: below --
2005-01-23 16:06 Kasper Sandberg
2005-01-23 16:28 ` Alessandro Suardi

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=20050124173426.GP2707@suse.de \
    --to=axboe@suse.de \
    --cc=alessandro.suardi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@metanurb.dk \
    --cc=tim@bcs4me.com \
    --cc=volker.armin.hemmann@tu-clausthal.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