[800] in linux-scsi channel archive
Re: Bug in scsi.c and sd.c (handling of CHECK_CONDITION)?
daemon@ATHENA.MIT.EDU (Eric Youngdale)
Sat Nov 11 14:47:58 1995
From: "Eric Youngdale" <eric@aib.com>
Date: Fri, 10 Nov 1995 12:06:41 -0500
In-Reply-To: "D.A.B. Niggemann" <dabn100@hermes.cam.ac.uk>
"Bug in scsi.c and sd.c (handling of CHECK_CONDITION)?" (Nov 8, 5:19pm)
To: "D.A.B. Niggemann" <dabn100@hermes.cam.ac.uk>, linux-scsi@vger.rutgers.edu
>I am going to test whether this error still occurs in 1.3.37 and see
>whether I can think of a patch to correct it. However, I have to admit
>the nesting of code in scsi_done (esp the fact that it is re-called during
>a REQUEST_SENSE) is confusing me a bit ( iam not sure what happens to the
>data transferred in previous read phase. Does a CHECK_CONDITION
>imply no data was transerred?
The problem is most likely still present in 1.3.37.
It sounds like scsi_done is doing the right thing - i.e. the error
is being passed up to the top level code in sd.c. If this is the correct
thing to do, then the only thing that needs fixing is that the interrupt
service routine in sd.c needs to be modified to recognize this case and
act appropriately.
>Finally, could somebody give a suugestion as to how I could modify the
>CD-ROM driver so as to make it return ENODATA to user programs if
>1. The device is actually a WORM drive.
>2. The device returns a BLANK_CHECK error.
Umm, exactly what type of device are you attempting to use here?
>I would be willing to invest some time in the following project:
>modifying sr.c to give a sw.c WORM driver.
>How soon is it intended that the Linux buffer cache will be modified to
>support SCSI block sizes other than 512K, 1024K or 2048K (for CDs only)?
>Is anybody working on this?
What block sizes do you need? The buffer cache should support
4096 bytes too, if you really need it.
-Eric
--
"The woods are lovely, dark and deep. But I have promises to keep,
And lines to code before I sleep, And lines to code before I sleep."
