From: Albert Lee <albertcc@tw.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: albertl@mail.com, YUP <yupadmin@gmail.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-ide@vger.kernel.org,
Sergei Shtylyov <sshtylyov@ru.mvista.com>,
Jeff Garzik <jeff@garzik.org>,
dougg@torque.net
Subject: Re: libata: CD and dvd devices not recognized
Date: Fri, 23 Mar 2007 11:40:36 +0800 [thread overview]
Message-ID: <46034C34.5000602@tw.ibm.com> (raw)
In-Reply-To: <20070322123729.14f11b96@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>>We have two possible solutions here:
>>a. Patch Ubuntu, such that the incorrect INQUIRY is fixed.
>>b. Patch kernel, such that the AOpen drives are blacklisted.
>> Each INQUIRY is inspected for the blacklisted drives.
>> If the INQUIRY looks wrong, the INQUIRY is rejected.
>>
>>I guess a. is the preferred solution...
>
>
> We have two problems here
>
> #1 Ubuntu got the inquiry command wrong
>
> #2 Until now we considered "INQUIRY" a safe command for SG_IO passthrough.
>
> We can't really take INQUIRY out of SG_IO so do we decide its the
> hardware vendors problem or do something cleverer in the filters ?
>
Maybe the SG_IO author has better idea (ccing Doug)?
BTW, in addition to the AOpen "INQUIRY with EVPD" problem, we have
another imperfect ATAPI drive (TORiSAN) that freezes when "READ >= 128KB".
(http://bugzilla.kernel.org/show_bug.cgi?id=6710)
We can limit "dev->max_sectors" to workaround the TORiSAN problem.
But I don't know whether "dev->max_sectors" also works for SG_IO?
If no, some user space application, unaware of the problem,
might send a "correct" READ that locks the drive completely.
--
albert
next prev parent reply other threads:[~2007-03-23 3:40 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 22:14 libata: CD and dvd devices not recognized YUP
2007-03-15 3:56 ` Albert Lee
2007-03-15 13:11 ` YUP
2007-03-15 17:32 ` Albert Lee
2007-03-16 10:16 ` YUP
2007-03-16 15:06 ` Albert Lee
2007-03-16 15:50 ` YUP
2007-03-17 13:29 ` Bartlomiej Zolnierkiewicz
2007-03-17 14:39 ` Albert Lee
2007-03-17 15:00 ` Bartlomiej Zolnierkiewicz
2007-03-17 18:38 ` YUP
2007-03-17 18:47 ` YUP
2007-03-17 19:12 ` Bartlomiej Zolnierkiewicz
2007-03-17 19:22 ` YUP
2007-03-17 20:07 ` Bartlomiej Zolnierkiewicz
2007-03-18 10:07 ` YUP
2007-03-18 15:10 ` Bartlomiej Zolnierkiewicz
2007-03-18 15:22 ` YUP
2007-03-18 15:54 ` Bartlomiej Zolnierkiewicz
2007-03-18 15:49 ` YUP
2007-03-18 22:48 ` YUP
2007-03-19 3:31 ` Albert Lee
2007-03-19 8:22 ` YUP
2007-03-19 8:29 ` Albert Lee
2007-03-19 12:10 ` Sergei Shtylyov
2007-03-19 19:35 ` YUP
2007-03-20 7:27 ` Albert Lee
2007-03-20 9:07 ` Albert Lee
2007-03-21 4:52 ` Albert Lee
2007-03-21 9:01 ` YUP
2007-03-22 6:06 ` Albert Lee
2007-03-22 7:09 ` Tejun Heo
2007-03-22 12:37 ` Alan Cox
2007-03-23 3:40 ` Albert Lee [this message]
2007-03-23 15:19 ` Douglas Gilbert
2007-03-26 5:50 ` Albert Lee
2007-03-22 14:50 ` Sergei Shtylyov
2007-03-23 3:21 ` Albert Lee
2007-03-19 23:02 ` YUP
2007-03-20 15:23 ` Sergei Shtylyov
2007-03-23 22:13 ` Bartlomiej Zolnierkiewicz
2007-03-26 5:53 ` Albert Lee
2007-03-18 6:42 ` YUP
2007-03-16 22:37 ` YUP
2007-03-17 3:24 ` Albert Lee
2007-03-17 9:09 ` YUP
2007-03-17 10:51 ` Albert Lee
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=46034C34.5000602@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=bzolnier@gmail.com \
--cc=dougg@torque.net \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
--cc=yupadmin@gmail.com \
/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).