From: Krishna Murthy <krmurthy@cisco.com>
To: SCSI Mailing List <linux-scsi@vger.kernel.org>
Cc: davmyers@cisco.com
Subject: Peripheral qualifier 1 not considered in scsi_probe_and_add_lun
Date: Thu, 27 Nov 2003 20:26:11 +0530 [thread overview]
Message-ID: <200311272026.11922.krmurthy@cisco.com> (raw)
In-Reply-To: <200311271849.15241.krmurthy@cisco.com>
Hi,
In scsi_probe_and_add_lun we check for Peripheral qualifier 3 (011b).
----------------------------------------------------------------------
/*
* result contains valid SCSI INQUIRY data.
*/
if ((result[0] >> 5) == 3) {
/*
* For a Peripheral qualifier 3 (011b), the SCSI
* spec says: The device server is not capable of
* supporting a physical device on this logical
* unit.
*
* For disks, this implies that there is no
* logical disk configured at sdev->lun, but there
* is a target id responding.
*/
SCSI_LOG_SCAN_BUS(3, printk(KERN_INFO
"scsi scan: peripheral qualifier of
3,"
" no device added\n"));
res = SCSI_SCAN_TARGET_PRESENT;
goto out_free_result;
}
------------------------------------------------------------------------------
Shouldn't the same apply for peripheral qualifier 1. This is what the SCSI
spec has to say about 1:
The device server is capable of supporting specified peripheral device type
on this logical unit. However the physical device is currently not connected
to this logical unit.
Thanx
N.C.Krishna Murthy
next prev parent reply other threads:[~2003-11-27 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 15:07 scsi_free_sdev and slave destroy Krishna Murthy
2003-11-25 15:23 ` James Bottomley
2003-11-27 13:19 ` scsi_scan_target and SCSI_2 Krishna Murthy
2003-11-27 14:56 ` Krishna Murthy [this message]
2003-11-27 15:55 ` Peripheral qualifier 1 not considered in scsi_probe_and_add_lun James Bottomley
2003-11-27 15:37 ` scsi_scan_target and SCSI_2 James Bottomley
2003-11-27 15:45 ` Krishna Murthy
2003-11-27 15:57 ` 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=200311272026.11922.krmurthy@cisco.com \
--to=krmurthy@cisco.com \
--cc=davmyers@cisco.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.