All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@suse.de>
Subject: [PATCH] cdrom sane fallback vs 2.4.20-pre1
Date: Sun, 11 Aug 2002 15:59:14 -0600	[thread overview]
Message-ID: <20020811215914.GC27048@codepoet.org> (raw)

Here is an update to cdrom.c.   SCSI-II devices are not required
to support the READ_CD packet command.  Currently, the cdrom
driver assumes that _all_ READ_CD packet command failures are due
to READ_CD being unsupported.  Obviously, there are a million
other reasons for a READ_CD packet command to fail.  Here at my
house, the most common reason for READ_CD failures is that my
kids have, once again, scratched up my CDs resulting in bad
sectors.  So the drive hits an uncorrectable error and thinks
that READ_CD is unsupported, and then trys again using READ_10
(which takes another a few seconds to fail and, of course, again
returns an L-EC Uncorrectable Error).

This patch teaches cdrom.c to only fall back to READ_10 when
the drive reports that we sent it an invalid command...

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

--- drivers/cdrom/cdrom.c~	Sun Aug 11 15:37:20 2002
+++ drivers/cdrom/cdrom.c	Sun Aug 11 15:37:24 2002
@@ -1916,6 +1916,7 @@
 {		
 	struct cdrom_device_ops *cdo = cdi->ops;
 	struct cdrom_generic_command cgc;
+	struct request_sense sense;
 	kdev_t dev = cdi->dev;
 	char buffer[32];
 	int ret = 0;
@@ -1951,9 +1952,11 @@
 		cgc.buffer = (char *) kmalloc(blocksize, GFP_KERNEL);
 		if (cgc.buffer == NULL)
 			return -ENOMEM;
+		memset(&sense, 0, sizeof(sense));
+		cgc.sense = &sense;
 		cgc.data_direction = CGC_DATA_READ;
 		ret = cdrom_read_block(cdi, &cgc, lba, 1, format, blocksize);
-		if (ret) {
+		if (ret && sense.sense_key==0x05 && sense.asc==0x20 && sense.ascq==0x00) {
 			/*
 			 * SCSI-II devices are not required to support
 			 * READ_CD, so let's try switching block size

             reply	other threads:[~2002-08-11 21:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-11 21:59 Erik Andersen [this message]
2002-08-13  2:58 ` [PATCH] cdrom sane fallback vs 2.4.20-pre1 Marcelo Tosatti
2002-08-13  4:12   ` Erik Andersen
2002-08-16  3:12     ` Oliver Xymoron
2002-08-13  8:42   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2002-08-13 14:13 James Bottomley
2002-08-13 15:48 ` Randy.Dunlap
2002-08-13 16:14   ` Jens Axboe
2002-08-13 16:21   ` James Bottomley
2002-08-13 16:25     ` Randy.Dunlap
2002-08-13 16:37       ` Jens Axboe
2002-08-13 17:10         ` James Bottomley

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=20020811215914.GC27048@codepoet.org \
    --to=andersen@codepoet.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.