From: Hannes Reinecke <hare@suse.de>
To: linux-scsi@vger.kernel.org
Cc: James Bottomley <jbottomley@parallels.com>,
George Martin <marting@netapp.com>,
Steffen Maier <maier@linux.vnet.ibm.com>,
Mike Christie <michaelc@cs.wisc.edu>,
Hannes Reinecke <hare@suse.de>
Subject: [PATCH][RFC] scsi: Use W_LUN for scanning
Date: Fri, 15 Mar 2013 10:46:11 +0100 [thread overview]
Message-ID: <1363340771-46925-1-git-send-email-hare@suse.de> (raw)
SAM advertises the use of a Well-known LUN (W_LUN) for scanning.
As this avoids exposing LUN 0 (which might be a valid LUN) for
all initiators it is the preferred method for LUN scanning on
some arrays.
So we should be using W_LUN for scanning, too. If the W_LUN is
not supported we'll fall back to use LUN 0.
For broken W_LUN implementations a new blacklist flag
'BLIST_NO_WLUN' is added.
Signed-off-by: Hannes Reinecke <hare@suse.de>
diff --git a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
index 3e58b22..f4ccdea 100644
--- a/drivers/scsi/scsi_scan.c
+++ b/drivers/scsi/scsi_scan.c
@@ -1312,6 +1312,7 @@ static int scsi_report_lun_scan(struct scsi_target *starget, int bflags,
unsigned int num_luns;
unsigned int retries;
int result;
+ int w_lun = SCSI_W_LUN_REPORT_LUNS;
struct scsi_lun *lunp, *lun_data;
u8 *data;
struct scsi_sense_hdr sshdr;
@@ -1337,11 +1338,20 @@ static int scsi_report_lun_scan(struct scsi_target *starget, int bflags,
return 0;
if (starget->no_report_luns)
return 1;
+ if (bflags & BLIST_NO_WLUN)
+ w_lun = 0;
+retry_report_lun_scan:
if (!(sdev = scsi_device_lookup_by_target(starget, 0))) {
- sdev = scsi_alloc_sdev(starget, 0, NULL);
- if (!sdev)
- return 0;
+ sdev = scsi_alloc_sdev(starget, w_lun, NULL);
+ if (!sdev) {
+ if (w_lun != 0) {
+ w_lun = 0;
+ sdev = scsi_alloc_sdev(starget, w_lun, NULL);
+ }
+ if (!sdev)
+ return 0;
+ }
if (scsi_device_get(sdev)) {
__scsi_remove_device(sdev);
return 0;
@@ -1418,6 +1428,18 @@ static int scsi_report_lun_scan(struct scsi_target *starget, int bflags,
}
if (result) {
+ if (w_lun != 0 && scsi_device_created(sdev)) {
+ /*
+ * W_LUN probably not supported, try with LUN 0
+ */
+ SCSI_LOG_SCAN_BUS(3, printk (KERN_INFO "scsi scan:"
+ "W_LUN not supported, try LUN 0\n"));
+ kfree(lun_data);
+ scsi_device_put(sdev);
+ __scsi_remove_device(sdev);
+ w_lun = 0;
+ goto retry_report_lun_scan;
+ }
/*
* The device probably does not support a REPORT LUN command
*/
diff --git a/include/scsi/scsi_devinfo.h b/include/scsi/scsi_devinfo.h
index cc1f3e7..ffb42b1 100644
--- a/include/scsi/scsi_devinfo.h
+++ b/include/scsi/scsi_devinfo.h
@@ -31,4 +31,5 @@
#define BLIST_MAX_512 0x800000 /* maximum 512 sector cdb length */
#define BLIST_ATTACH_PQ3 0x1000000 /* Scan: Attach to PQ3 devices */
#define BLIST_NO_DIF 0x2000000 /* Disable T10 PI (DIF) */
+#define BLIST_NO_WLUN 0x4000000 /* Disable W_LUN scanning */
#endif
next reply other threads:[~2013-03-15 9:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 9:46 Hannes Reinecke [this message]
2013-03-15 15:54 ` [PATCH][RFC] scsi: Use W_LUN for scanning Steffen Maier
2013-03-17 21:50 ` Steffen Maier
2013-03-18 15:25 ` Hannes Reinecke
2013-03-15 21:22 ` Douglas Gilbert
2013-04-06 9:08 ` James Bottomley
2013-04-07 13:31 ` Hannes Reinecke
2013-04-07 14:49 ` James Bottomley
2013-04-07 15:59 ` Douglas Gilbert
2013-04-07 16:15 ` James Bottomley
2013-04-07 16:34 ` Douglas Gilbert
2013-04-07 17:37 ` 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=1363340771-46925-1-git-send-email-hare@suse.de \
--to=hare@suse.de \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=maier@linux.vnet.ibm.com \
--cc=marting@netapp.com \
--cc=michaelc@cs.wisc.edu \
/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