From: James Bottomley <James.Bottomley@SteelEye.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "Darrick J. Wong" <djwong@us.ibm.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Douglas Gilbert <dougg@torque.net>
Subject: Re: [PATCH v2] libata: Simulate REPORT LUNS for ATAPI devices
Date: Mon, 11 Dec 2006 10:44:49 -0600 [thread overview]
Message-ID: <1165855489.2791.7.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <457D8637.5070707@garzik.org>
On Mon, 2006-12-11 at 11:24 -0500, Jeff Garzik wrote:
> Darrick J. Wong wrote:
> > The Quantum GoVault SATAPI removable disk device returns ATA_ERR in
> > response to a REPORT LUNS packet. If this happens to an ATAPI device
> > that is attached to a SAS controller (this is the case with sas_ata),
> > the device does not load because SCSI won't touch a "SCSI device"
> > that won't report its LUNs. Since most ATAPI devices don't support
> > multiple LUNs anyway, we might as well fake a response like we do for
> > ATA devices.
> >
> > Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
>
> I'm leaning towards applying this, perhaps with a module option that
> allows experimenters to revert back to the older behavior.
>
> Any chance you could be talked into tackling some of the SAT
> translation-related items Doug G mentioned? I'm almost certain there
> are some info pages we should be returning, but are not, at the very least.
I thought we were closing in on agreeing that the SPC/MMC
inconsistencies made this the correct candidate fix.
James
diff --git a/drivers/scsi/scsi_devinfo.c b/drivers/scsi/scsi_devinfo.c
index ce63044..9d5e75b 100644
--- a/drivers/scsi/scsi_devinfo.c
+++ b/drivers/scsi/scsi_devinfo.c
@@ -7,6 +7,7 @@
#include <linux/proc_fs.h>
#include <linux/seq_file.h>
+#include <scsi/scsi.h>
#include <scsi/scsi_device.h>
#include <scsi/scsi_devinfo.h>
@@ -439,6 +440,11 @@ int scsi_get_device_flags(struct scsi_de
return devinfo->flags;
}
}
+ /* MMC devices can return SCSI-3 compliance and yet still not
+ * support REPORT LUNS, so make them act as BLIST_NOREPORTLUN
+ * unless BLIST_REPORTLUN2 is specifically set */
+ if (sdev->type == TYPE_ROM && (bflags & BLIST_REPORTLUN2) == 0)
+ bflags |= BLIST_NOREPORTLUN;
return bflags;
}
diff --git a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
next prev parent reply other threads:[~2006-12-11 16:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 23:02 libata: Simulate REPORT LUNS for ATAPI devices when not supported Darrick J. Wong
2006-12-04 23:12 ` Jeff Garzik
2006-12-04 23:32 ` [PATCH v2] libata: Simulate REPORT LUNS for ATAPI devices Darrick J. Wong
2006-12-07 12:20 ` Jeff Garzik
2006-12-07 15:47 ` Douglas Gilbert
2006-12-07 18:09 ` James Bottomley
2006-12-07 19:13 ` Douglas Gilbert
2006-12-11 16:24 ` Jeff Garzik
2006-12-11 16:44 ` James Bottomley [this message]
2006-12-11 16:59 ` Jeff Garzik
2006-12-12 22:24 ` Darrick J. Wong
2006-12-13 16:10 ` James Bottomley
2006-12-13 17:38 ` Darrick J. Wong
2006-12-13 17:57 ` James Bottomley
2006-12-13 18:56 ` Patrick Mansfield
2006-12-13 20:06 ` Darrick J. Wong
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=1165855489.2791.7.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=djwong@us.ibm.com \
--cc=dougg@torque.net \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--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
Powered by JetHome