[SCSI] stex: fix scan of nonexistent lun

During a manual scan, a user can send command to a nonexistent
lun, precisely at the point of max_lun. Normally it's possible
(but not required) that the firmware has the knowledge that it
is an invalid lun. In the particular case when max_lun is 256,
however, the nonexistent lun 256 will be confused with lun 0,
because the lun member in a request message is only u8, and 256
will become 0. So we need to fix the problem, at least, at the
driver level.

Signed-off-by: Ed Lin <ed.lin@promise.com>
Signed-off-by: James Bottomley <James.Bottomley@suse.de>
This commit is contained in:
Ed Lin 2009-12-18 17:34:51 -08:00 committed by James Bottomley
parent a70757ba9a
commit 91e6ecada7
1 changed files with 5 additions and 0 deletions

View File

@ -623,6 +623,11 @@ stex_queuecommand(struct scsi_cmnd *cmd, void (* done)(struct scsi_cmnd *))
} }
break; break;
case INQUIRY: case INQUIRY:
if (lun >= host->max_lun) {
cmd->result = DID_NO_CONNECT << 16;
done(cmd);
return 0;
}
if (id != host->max_id - 1) if (id != host->max_id - 1)
break; break;
if (!lun && !cmd->device->channel && if (!lun && !cmd->device->channel &&