From: Kurt Garloff <garloff@suse.de>
To: Linux SCSI list <linux-scsi@vger.kernel.org>
Cc: Patrick Mansfield <patmans@us.ibm.com>
Subject: [PATCH 1/3] Try LUN 1 and use bflags
Date: Wed, 29 Mar 2006 22:11:47 +0200 [thread overview]
Message-ID: <20060329201147.GH7919@tpkurt.suse.de> (raw)
In-Reply-To: <20060329201020.GG7919@tpkurt.suse.de>
[-- Attachment #1: Type: text/plain, Size: 2227 bytes --]
From: Kurt Garloff <garloff@suse.de>
Subject: Tolerate PQ 3 at LUN 0 for scanning
Patch-mainline:
References: 158532
Some devices report a peripheral qualifier of 3 for LUN 0; with the original
code, we would still try a REPORT_LUNS scan (if SCSI level is >= 3 or if we
have the BLIST_REPORTLUNS2 passed in), but NOT any sequential scan.
Also, the device at LUN 0 (which is not connected according to the PQ) is not
registered with the OS.
Unfortunately, SANs exist that are SCSI-2 and do NOT support REPORT_LUNS, but
report a unknown device with PQ 3 on LUN 0. We still need to scan them, and
most probably we even need BLIST_SPARSELUN (and BLIST_LARGELUN). See the bug
reference for an infamous example.
This is patch 1/3:
If we end up in sequential scan, at least try LUN 1 for devices
that reported a PQ of 3 for LUN 0.
Also return blacklist flags, even for PQ3 devices.
Acked-by:
Signed-off-by: Kurt Garloff <garloff@suse.de>
Index: linux-2.6.16/drivers/scsi/scsi_scan.c
===================================================================
--- linux-2.6.16.orig/drivers/scsi/scsi_scan.c
+++ linux-2.6.16/drivers/scsi/scsi_scan.c
@@ -860,6 +860,8 @@ static int scsi_probe_and_add_lun(struct
if (scsi_probe_lun(sdev, result, result_len, &bflags))
goto out_free_result;
+ if (bflagsp)
+ *bflagsp = bflags;
/*
* result contains valid SCSI INQUIRY data.
*/
@@ -887,8 +889,6 @@ static int scsi_probe_and_add_lun(struct
sdev->lockable = 0;
scsi_unlock_floptical(sdev, result);
}
- if (bflagsp)
- *bflagsp = bflags;
}
out_free_result:
@@ -945,11 +945,13 @@ static void scsi_sequential_lun_scan(str
sparse_lun = 0;
/*
- * If not sparse lun and no device attached at LUN 0 do not scan
- * any further.
- */
+ * If LUN0 did respond, but did not have an attachable LUN (PQ=3),
+ * we do NOT abort the sequential scan yet, let's try one more
+ * LUN and only abort the scan if we don't find anything there.
+ *
if (!sparse_lun && (lun0_res != SCSI_SCAN_LUN_PRESENT))
return;
+ */
/*
* If less than SCSI_1_CSS, and no special lun scaning, stop
--
Kurt Garloff, Head Architect Linux R&D, Novell Inc.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-03-29 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 20:10 [PATCH 0/3] SCSI scanning for PQ3 devs Kurt Garloff
2006-03-29 20:11 ` Kurt Garloff [this message]
2006-03-31 16:39 ` [PATCH 1/3] Try LUN 1 and use bflags Patrick Mansfield
2006-03-29 20:12 ` [PATCH 2/3] Better log messages for PQ3 devs Kurt Garloff
2006-03-29 20:30 ` Matthew Wilcox
2006-03-29 22:12 ` Kurt Garloff
2006-03-29 22:23 ` James Bottomley
2006-03-29 20:13 ` [PATCH 3/3] BLIST_ATTACH_PQ3 flags Kurt Garloff
2006-04-03 13:16 ` [PATCH 1/3] Try LUN 1 and use bflags Kurt Garloff
2006-04-03 13:18 ` [PATCH 2/3] Better log messages for PQ3 devs Kurt Garloff
2006-04-03 13:20 ` [PATCH 3/3] BLIST_ATTACH_PQ3 flags Kurt Garloff
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=20060329201147.GH7919@tpkurt.suse.de \
--to=garloff@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.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).