From: Jens Axboe <axboe@suse.de>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] fix cdrom mt rainier probe
Date: Fri, 16 Jul 2004 14:25:55 +0200 [thread overview]
Message-ID: <20040716122554.GD2025@suse.de> (raw)
In-Reply-To: <1089938380.3667.19.camel@patibmrh9>
On Thu, Jul 15 2004, Pat LaVarre wrote:
> 1) The first part changes cdrom_open to check CDC_RAM earlier in an
> FMODE_WRITE open i.e. before open_for_data. I'm asking you to choose to
> check earlier or not.
>
> 2) The second part draws your attention to a set_disk_ro I actually did
> not delete. That remaining set_disk_ro dynamically forces ro true in
> response to particular write errors. The /* != scsi/sr.c */ text of the
> comment I used to draw you attention to that source line means to say
> that this is an asymmetry between ide/ide-cd.c and scsi/sr.c, in that
> only ide/ide-cd.c works this hard. I'm asking you to choose to delete
> that call to set_disk_ro, to comment on its asymmetry, or to leave it
> unchanged.
>
> 3, 4) The last two parts of the patch merely delete the once-per-plugin
> calls to set_disk_ro.
>
> Pat LaVarre
>
> diff -urp linux-2.6.8-rc1/drivers/cdrom/cdrom.c linux-2.6.8-rc1-pel/drivers/cdrom/cdrom.c
> --- linux-2.6.8-rc1/drivers/cdrom/cdrom.c 2004-07-13 08:26:02.000000000 -0600
> +++ linux-2.6.8-rc1-pel/drivers/cdrom/cdrom.c 2004-07-15 18:21:48.564652904 -0600
> @@ -892,13 +892,16 @@ int cdrom_open(struct cdrom_device_info
> if ((fp->f_flags & O_NONBLOCK) && (cdi->options & CDO_USE_FFLAGS)) {
> ret = cdi->ops->open(cdi, 1);
> } else {
> + if (fp->f_mode & FMODE_WRITE) {
> + ret = -EROFS;
> + if (!CDROM_CAN(CDC_RAM))
> + goto err;
> + }
> ret = open_for_data(cdi);
> if (ret)
> goto err;
> if (fp->f_mode & FMODE_WRITE) {
> ret = -EROFS;
> - if (!CDROM_CAN(CDC_RAM))
> - goto err;
> if (cdrom_open_write(cdi))
> goto err;
> ret = 0;
This looks strange - cdrom_open_write() is the one that checks whether
the media is suitable for writing or not. In fact, it looks as if just
transposing the two checks should be fine:
if (fp->f_mode & FMODE_WRITE) {
ret = -EROFS;
if (cdrom_open_write(cdi))
goto err;
if (!CDROM_CAN(CDC_RAM))
goto err;
ret = 0;
}
> diff -urp linux-2.6.8-rc1/drivers/ide/ide-cd.c linux-2.6.8-rc1-pel/drivers/ide/ide-cd.c
> --- linux-2.6.8-rc1/drivers/ide/ide-cd.c 2004-07-13 08:26:05.000000000 -0600
> +++ linux-2.6.8-rc1-pel/drivers/ide/ide-cd.c 2004-07-15 14:38:23.000000000 -0600
> @@ -790,7 +790,7 @@ static int cdrom_decode_status(ide_drive
> */
> if (rq_data_dir(rq) == WRITE) {
> printk("ide-cd: media marked write protected\n");
> - set_disk_ro(drive->disk, 1);
> + set_disk_ro(drive->disk, 1); /* != scsi/sr.c */
> }
This needs to go as well, unless you mark it writable again after close
of this media.
> /* No point in retrying after an illegal
> @@ -3248,9 +3248,8 @@ int ide_cdrom_setup (ide_drive_t *drive)
> nslots = ide_cdrom_probe_capabilities (drive);
>
> /*
> - * set correct block size and read-only for non-ram media
> + * set correct block size
> */
> - set_disk_ro(drive->disk, !CDROM_CONFIG_FLAGS(drive)->ram);
> blk_queue_hardsect_size(drive->queue, CD_FRAMESIZE);
>
> #if 0
> diff -urp linux-2.6.8-rc1/drivers/scsi/sr.c linux-2.6.8-rc1-pel/drivers/scsi/sr.c
> --- linux-2.6.8-rc1/drivers/scsi/sr.c 2004-07-13 08:26:16.000000000 -0600
> +++ linux-2.6.8-rc1-pel/drivers/scsi/sr.c 2004-07-15 14:29:34.000000000 -0600
> @@ -775,9 +775,6 @@ static void get_capabilities(struct scsi
> ""
> };
>
> - /* Set read only initially */
> - set_disk_ro(cd->disk, 1);
> -
> /* allocate a request for the TEST_UNIT_READY */
> SRpnt = scsi_allocate_request(cd->device, GFP_KERNEL);
> if (!SRpnt) {
> @@ -885,7 +882,6 @@ static void get_capabilities(struct scsi
> if ((cd->cdi.mask & (CDC_DVD_RAM | CDC_MRW_W | CDC_RAM)) !=
> (CDC_DVD_RAM | CDC_MRW_W | CDC_RAM)) {
> cd->device->writeable = 1;
> - set_disk_ro(cd->disk, 0);
> }
>
> scsi_release_request(SRpnt);
These are fine.
--
Jens Axboe
next prev parent reply other threads:[~2004-07-16 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1089741428.3806.3.camel@patibmrh9>
2004-07-13 20:55 ` [PATCH] fix cdrom mt rainier probe Pat LaVarre
2004-07-14 5:41 ` Jens Axboe
2004-07-14 23:34 ` Pat LaVarre
2004-07-16 0:39 ` Pat LaVarre
2004-07-16 12:25 ` Jens Axboe [this message]
2004-07-16 12:28 ` Jens Axboe
2004-07-16 15:58 ` Pat LaVarre
2004-07-16 16:02 ` Jens Axboe
2004-07-16 16:19 ` Pat LaVarre
2004-07-16 17:51 ` Jens Axboe
2004-07-18 0:43 ` Pat LaVarre
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=20040716122554.GD2025@suse.de \
--to=axboe@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=p.lavarre@ieee.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