On Wed, 2013-02-13 at 16:06 +0100, Hannes Reinecke wrote: > shost->max_lun is only ever useful when doing a sequential > scan as we need to limit the number of devices to scan there. > For report lun scan we should allow _any_ reported LUN number > as long as the LLDD supports 64 bit LUNs. > > So add a new flag 'support_64bit_luns' to the scsi host and > modify report lun scan to not check for max_luns during > scanning if that flag is set. This will get rid of the > annoying 'lunXXXX has a LUN larger than allowed ...' > message and allow scanning to continue. What advantage does this have over setting max_lun to ~0? Plus, if we're going to advertise 64 bit lun support I'd rather have us be actually capable of it ... luns are handled as 32 bit numbers in the mid layer currently. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
