All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Dake <sdake@mvista.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: why store the search type in the ieee name field?
Date: Tue, 11 Feb 2003 10:38:59 -0700	[thread overview]
Message-ID: <3E493533.7000508@mvista.com> (raw)
In-Reply-To: <1044981839.1774.10.camel@mulgrave>

When I looked at this code originally, it looked correct, I was just 
wondering why have an identifier field. I understand the reasoning now.

Thanks
-steve

James Bottomley wrote:

>On Tue, 2003-02-11 at 10:20, Patrick Mansfield wrote:
>  
>
>>On Mon, Feb 10, 2003 at 05:12:54PM -0600, James Bottomley wrote:
>>    
>>
>>>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.
>>>      
>>>
>>It should fill in the rest of the 'name' and append a '\0', or return a
>>failure.
>>    
>>
>
>No, look at the code.  After doing name[0] = hex_str[...
>it then does a strcat.  If name is full of junk, strcat will append
>after the first \0 it finds (which may be off the end of the name
>field).  It only works because name[1] is zero but nothing seems to
>clear it.  I'm hoping it's being cleared in a piece of code I haven't
>found yet...
>
>James
>
>
>
>
>
>  
>


      parent reply	other threads:[~2003-02-11 17:38 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
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 [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=3E493533.7000508@mvista.com \
    --to=sdake@mvista.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.