From: Peter Osterlund <petero2@telia.com>
To: "Tony A. Lambley" <tal@vextech.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: growisofs stopped working with 2.6.8
Date: 16 Aug 2004 20:14:02 +0200 [thread overview]
Message-ID: <m3ekm7osr9.fsf@telia.com> (raw)
In-Reply-To: <1092679156.2393.8.camel@bony>
"Tony A. Lambley" <tal@vextech.net> writes:
> It still fails, but I get a different message with the patch:
>
> $ growisofs -Z /dev/dvd=file.iso
> Executing 'builtin_dd if=file.iso of=/dev/dvd obs=32k seek=0'
> :-( unable to PREVENT MEDIA REMOVAL: Operation not permitted
>
> K3B fails with the same message as above.
>
> As you say, it does indeed burn fine as root.
The patch below is needed for a start, but it's not enough, because
growisofs opens the device in read-only mode, so WRITE_10 fails
anyway.
--- drivers/block/scsi_ioctl.c~cdrw-filter 2004-08-16 17:13:23.000000000 +0200
+++ drivers/block/scsi_ioctl.c 2004-08-16 18:44:15.000000000 +0200
@@ -146,6 +146,13 @@
safe_for_read(GPCMD_READ_TOC_PMA_ATIP),
safe_for_read(GPCMD_REPORT_KEY),
safe_for_read(GPCMD_SCAN),
+ safe_for_read(GPCMD_GET_CONFIGURATION),
+ safe_for_read(GPCMD_READ_FORMAT_CAPACITIES),
+ safe_for_read(GPCMD_GET_EVENT_STATUS_NOTIFICATION),
+ safe_for_read(GPCMD_GET_PERFORMANCE),
+
+ safe_for_write(GPCMD_PREVENT_ALLOW_MEDIUM_REMOVAL),
+ safe_for_write(GPCMD_FLUSH_CACHE),
/* Basic writing commands */
safe_for_write(WRITE_6),
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
prev parent reply other threads:[~2004-08-16 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1092674287.3021.19.camel@bony>
2004-08-16 16:01 ` growisofs stopped working with 2.6.8 Alan Cox
2004-08-16 17:59 ` Tony A. Lambley
2004-08-16 18:14 ` Peter Osterlund [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=m3ekm7osr9.fsf@telia.com \
--to=petero2@telia.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tal@vextech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).