From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <jbottomley@parallels.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/5] scsi_scan: Restrict sequential scan to 256 LUNs
Date: Fri, 28 Mar 2014 06:19:24 -0700 [thread overview]
Message-ID: <533576DC.1060806@suse.de> (raw)
In-Reply-To: <20140328124747.GA18866@infradead.org>
On 03/28/2014 05:47 AM, Christoph Hellwig wrote:
> On Fri, Mar 28, 2014 at 01:22:15AM -0700, Hannes Reinecke wrote:
>> Because there is no guarantee that pre-SCSI-3 devices (or devices
>> announcing to be pre-SCSI-3) will not allow to scan more than 256
>> devices.
>> Thinking of older Symmetrix here with their weird 'SPC-3 masking as
>> SCSI-2' habit.
>
> Don't we have a blist entry for those to use REPORT LUNS anyway?
Symmetrix was just an example of weirdness ...
>>
>> Also currently we're allowing to scan beyond 256 without any
>> restrictions there might be installations out there which rely on
>> this behaviour.
>>
>> Hence this flag.
>
> Which doesn't really have an effect as-is as it's never set.
>
Because currently there are no target which would require them.
Obviously. But that doesn't mean there won't be any.
Note, this is just a safety net for backwards compability.
If you think we won't need it of course we can remove it.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-03-28 13:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 11:05 [PATCH 0/5][RFC] Support 64-bit LUNs Hannes Reinecke
2013-12-10 11:05 ` [PATCH 1/5] scsi: Remove CONFIG_SCSI_MULTI_LUN Hannes Reinecke
2014-03-27 14:47 ` Christoph Hellwig
2013-12-10 11:05 ` [PATCH 2/5] scsi_scan: Restrict sequential scan to 256 LUNs Hannes Reinecke
2014-03-27 14:49 ` Christoph Hellwig
2014-03-28 8:22 ` Hannes Reinecke
2014-03-28 12:47 ` Christoph Hellwig
2014-03-28 13:19 ` Hannes Reinecke [this message]
2013-12-10 11:05 ` [PATCH 3/5] qla2xxx: Restrict max_luns to 16-bit for older HBAs Hannes Reinecke
2013-12-10 18:26 ` Chad Dupuis
2014-05-15 6:38 ` Christoph Hellwig
2014-05-15 8:47 ` Hannes Reinecke
2013-12-10 11:05 ` [PATCH 4/5] scsi: use 64-bit LUNs Hannes Reinecke
2014-03-27 14:52 ` Christoph Hellwig
2013-12-10 11:05 ` [PATCH 5/5] scsi: use 64-bit value for 'max_luns' Hannes Reinecke
2014-03-27 14:52 ` Christoph Hellwig
2014-05-15 6:38 ` [PATCH 0/5][RFC] Support 64-bit LUNs Christoph Hellwig
2014-05-15 6:57 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2014-05-20 11:03 [PATCHv2 0/5] " Hannes Reinecke
2014-05-20 11:03 ` [PATCH 2/5] scsi_scan: Restrict sequential scan to 256 LUNs Hannes Reinecke
2014-05-22 9:08 ` 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=533576DC.1060806@suse.de \
--to=hare@suse.de \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.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 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).