From: Luben Tuikov <ltuikov@yahoo.com>
To: James.Smart@Emulex.Com, "Darrick J. Wong" <djwong@us.ibm.com>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alexis Bruemmer <alexisb@us.ibm.com>,
James Bottomley <james.bottomley@steeleye.com>
Subject: Re: [PATCH] aic94xx: Use request_firmware() to provide SAS address if the adapter lacks one
Date: Wed, 10 Oct 2007 12:38:42 -0700 (PDT) [thread overview]
Message-ID: <105757.49287.qm@web31805.mail.mud.yahoo.com> (raw)
In-Reply-To: <470CE78B.2080509@emulex.com>
--- James Smart <James.Smart@Emulex.Com> wrote:
> Here's one pro for setting WWNs at arbitrary times...
> If the box is migrating applications (say containers) that want
> different SAN connectivity, where that connectivity (view) is based
> on their WWN, it would be really nice to selectively set the WWN and
> not touch the SAN config.
No. The WWN stays the same and the SAN is re-configured to be
aware of the node migration. Access patterns could be more
complex than just a single portal allowing access to/from the
SAN from/to the node.
WWN is supposed to be persistent. This is what it actually is.
It is NOT supposed to be "(auto)generated" and/or changed at a whim.
This also has security implications, and enterprise networks may
refuse to use software (read "kernel") which allows for arbitrary
changes to a node's WWN.
If access to a node is compromised, a rogue agent may change
the node's WWN in order to access SAN zones that it normally
will be denied access to.
Luben
prev parent reply other threads:[~2007-10-10 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 21:25 [PATCH] aic94xx: Use request_firmware() to provide SAS address if the adapter lacks one Darrick J. Wong
2007-10-08 22:48 ` Andrew Vasquez
2007-10-08 23:50 ` Darrick J. Wong
2007-10-09 0:12 ` Andrew Vasquez
2007-10-09 15:29 ` James Smart
2007-10-09 16:41 ` Andrew Vasquez
2007-10-09 17:06 ` Darrick J. Wong
2007-10-10 14:54 ` James Smart
2007-10-10 15:40 ` Jeff Garzik
2007-10-10 19:38 ` Luben Tuikov [this message]
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=105757.49287.qm@web31805.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=James.Smart@Emulex.Com \
--cc=alexisb@us.ibm.com \
--cc=andrew.vasquez@qlogic.com \
--cc=djwong@us.ibm.com \
--cc=james.bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--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