From: James Bottomley <James.Bottomley@SteelEye.com>
To: Swen Schillig <swen@vnet.ibm.com>
Cc: linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org,
schmichr@de.ibm.com
Subject: Re: [PATCH 3/3] zfcp: Don't report device as LUN 0 to SCSI stack
Date: Sun, 17 Jun 2007 15:50:12 -0500 [thread overview]
Message-ID: <1182113412.19498.7.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <200705291529.54785.swen@vnet.ibm.com>
On Tue, 2007-05-29 at 15:29 +0200, Swen Schillig wrote:
> From: Christof Schmitt <schmichr@de.ibm.com>
>
> zfcp reported units to the SCSI stack starting
> with number 0. LUN 0 reported to the SCSI stack is usually
> not the FCP LUN 0. When scanning for devices,
> the SCSI stack tried to issue a REPORT LUN command to LUN 0.
> The current design for zfcp does not want the SCSI stack to scan
> for devices, since they are configured explicitly via sysfs.
> This patch changes the numbering to always start with LUN 1 and therefore
> prevent the SCSI stack sending REPORT LUN command.
As a general principle, this does sound to be wrong (at least shifting
the LUNs). Wouldn't something like the existing blacklist preventing
the REPORT LUN command from being sent be more appropriate?
James
next prev parent reply other threads:[~2007-06-17 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 13:29 [PATCH 3/3] zfcp: Don't report device as LUN 0 to SCSI stack Swen Schillig
2007-06-17 20:50 ` James Bottomley [this message]
2007-06-18 8:47 ` Hannes Reinecke
2007-06-18 13:04 ` Swen Schillig
2007-06-18 13:56 ` Heiko Carstens
2007-06-18 14:25 ` 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=1182113412.19498.7.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=schmichr@de.ibm.com \
--cc=swen@vnet.ibm.com \
/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