public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Steven Dake <sdake@mvista.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: why store the search type in the ieee name field?
Date: 10 Feb 2003 17:12:54 -0600	[thread overview]
Message-ID: <1044918776.1776.257.camel@mulgrave> (raw)
In-Reply-To: <3E482B9E.40803@mvista.com>

On Mon, 2003-02-10 at 16:45, Steven Dake wrote:
> Folks,
> 
> I was wondering the reasoning behind the code
> 
> scsi_scan:734
>         /*
>          * All OK - store ID
>          */
>       name[0] = hex_str[id_search->id_type];
> 
> This corrupts a perfectly good IEEE unique identifier (WWN for FC 
> drives).  Is there some usage for this in user space?

Erm, it's appending the type to the beginning of the name string
(although it does seem to be relying on the sysfs name field being zero
filled).  I don't see any corruption since the inquiry fields and unique
name name follows this byte.

You get the identifier it found from the sysfs name file for the
device.  The first byte tells you what type of unique name you're
dealing with.

James



  reply	other threads:[~2003-02-10 23:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 22:45 why store the search type in the ieee name field? Steven Dake
2003-02-10 23:12 ` James Bottomley [this message]
2003-02-11 16:20   ` Patrick Mansfield
2003-02-11 16:43     ` James Bottomley
2003-02-11 16:46       ` Patrick Mansfield
2003-02-11 17:38       ` Steven Dake

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=1044918776.1776.257.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sdake@mvista.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