From: "Tony A. Lambley" <tal@vextech.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-scsi@vger.kernel.org
Subject: Re: growisofs stopped working with 2.6.8
Date: Mon, 16 Aug 2004 13:59:16 -0400 [thread overview]
Message-ID: <1092679156.2393.8.camel@bony> (raw)
In-Reply-To: <1092672062.20838.29.camel@localhost.localdomain>
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.
On Mon, 2004-08-16 at 12:01, Alan Cox wrote:
> On Llu, 2004-08-16 at 17:38, Tony A. Lambley wrote:
> > Hi, burning a dvd iso now fails :(
> >
> > $ growisofs -Z /dev/hdc=file.iso
> > :-( unable to GET CONFIGURATION: Operation not permitted
> > :-( non-MMC unit?
>
> We fixed some security holes. In doing so we tightened up so a few apps
> that worked before no longer work except as root. Thanks for the error
> message. Thats helpful as it suggests the following patch.
>
> (and does it help K3B ?)
>
>
>
>
>
>
> ______________________________________________________________________
> --- drivers/block/scsi_ioctl.c~ 2004-08-16 18:01:36.627301624 +0100
> +++ drivers/block/scsi_ioctl.c 2004-08-16 18:01:36.627301624 +0100
> @@ -146,6 +146,7 @@
> 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),
>
> /* Basic writing commands */
> safe_for_write(WRITE_6),
next prev parent reply other threads:[~2004-08-16 17:59 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 [this message]
2004-08-16 18:14 ` Peter Osterlund
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=1092679156.2393.8.camel@bony \
--to=tal@vextech.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).