From: Dave Wysochanski <davidw@netapp.com>
To: Christoph Hellwig <hch@lst.de>,
usb-storage@lists.one-eyed-alien.net, stern@rowland.harvard.edu
Cc: James.Bottomley@steeleye.com, michaelc@cs.wisc.edu,
linux-scsi@vger.kernel.org, hare@suse.de, "Kraft,
Claire" <Claire.Kraft@netapp.com>,
"Shenoy, Raghavendra" <Raghavendra.Shenoy@netapp.com>,
"George, Martin" <marting@netapp.com>,
"Nair, Vinod K" <nvinod@netapp.com>
Subject: Re: [PATCH] Don't add scsi_device for devices that return PQ=1, PDT=0x1f
Date: Mon, 07 Aug 2006 02:03:10 -0400 [thread overview]
Message-ID: <44D6D79E.3020304@netapp.com> (raw)
In-Reply-To: <20060805120103.GA22356@lst.de>
Christoph Hellwig wrote:
> On Thu, Jul 27, 2006 at 04:30:36PM -0400, Dave Wysochanski wrote:
> > Some targets may return PQ=1 and PDT=0x1f to indicate no LUN is mapped
> > (Netapp targets do this). This seems like a valid way to indicate no
> > LUN mapped according to SPC-3.
> >
> > However, the current scsi_probe_and_add_lun() code adds a scsi_device
> > for targets that return PQ=1 and PDT=0x1f. This causes LUNs of type
> > "UNKNOWN" to show up in /proc/scsi/scsi when no LUNs are mapped.
> > In addition, subsequent rescans fail to recognize LUNs that may be
> > added on the target, unless preceded by a write to the delete attribute
> > of the "UNKNOWN" LUN.
> >
> > This patch addresses this problem by skipping over the scsi_add_lun()
> > when PQ=1,PDT=0x1f is encountered, and just returns
> > SCSI_SCAN_TARGET_PRESENT.
> >
> > If there are objections to this patch, I can add a BLIST flag and entry
> > for Netapp targets but would like to avoid that if possible, since it
> > seems like the current code might be closer to SPC-3 with this patch.
>
> If you look at scsi_probe_and_add_lun in current mainline we already
> have a check for PDT=0x1f, keyed of a blacklist flag in the scsi target.
> The comment above it says it's for USB UFI. It's missing the PQ=1
> check, though. Can you reassure with the USB storage people that USB
> UFI indeed sets that periphal qualifier aswell (I'd guess so as IIRC
> that standard references SPC). If that's the case replace that check
> with your version and remove the target flag.
>
Yeah, I saw that. If you look at that patch description from Alan, he
states the PQ=0 for these devices:
http://marc.theaimsgroup.com/?l=linux-scsi&m=113951679626087&w=2
Unfortunately USB UFI 1.0 spec has "reserved" where the PQ bits normally are,
so maybe that's why there's only a check for PDT=0x1f? Alan or someone
from the usb-storage list, can you confirm this is correct (PQ really
"reserved" is 0 for the USB UFI devices)? I thought I had a USB floppy
lying around but no luck.
Also, it does not look like pdt_1f_for_no_lun flag Alan added is used.
Alan do you intend on submitting the patch to the USB slave_alloc() function
as you mentioned?
I'm not sure Alan's pdt_1f_for_no_lun flag should be used in my case,
since I would want to set it based on vid/pid - most appropriate in
scsi_get_device_flags() - and he wanted to set it in slave_alloc().
Maybe setting it in 2 different places for different devices is ok
though - your call.
> Also I'd suggest using a comment similar to the one in your patch to
> describe it, but mention USB UFI and Netapp targets as real world
> examples for this behaviour aswell.
>
Sure.
next prev parent reply other threads:[~2006-08-07 6:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 20:30 [PATCH] Don't add scsi_device for devices that return PQ=1, PDT=0x1f Dave Wysochanski
2006-08-05 12:01 ` Christoph Hellwig
2006-08-07 6:03 ` Dave Wysochanski [this message]
2006-08-07 14:45 ` Alan Stern
2006-08-08 15:34 ` Christoph Hellwig
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=44D6D79E.3020304@netapp.com \
--to=davidw@netapp.com \
--cc=Claire.Kraft@netapp.com \
--cc=James.Bottomley@steeleye.com \
--cc=Raghavendra.Shenoy@netapp.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=marting@netapp.com \
--cc=michaelc@cs.wisc.edu \
--cc=nvinod@netapp.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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.