linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: lsscsi-0.17 released
Date: Wed, 22 Feb 2006 10:37:31 -0800	[thread overview]
Message-ID: <20060222183731.GB12542@kroah.com> (raw)
In-Reply-To: <43FCA686.5020508@torque.net>

On Wed, Feb 22, 2006 at 12:59:34PM -0500, Douglas Gilbert wrote:
> Greg KH wrote:
> >>/sys/class/scsi_device/<hcil>/device/block symlink
> >>changed to ".../block:sd<x>" breaking lsscsi 0.16 (and
> >>earlier) and sg_map26 (in sg3_utils).
> 
> > It was changed as there would be more than one "block" symlink in a
> > device's directory if more than one block device was attached to a
> > single struct device.  For example, ub and multi-lun devices (there were
> > other reports of this happening for scsi devices too at the time from
> > what I remember.)
> 
> A "scsi_device" is a logical unit, hence the "l" at
> the end of the "<hcil>" acronym in the above path.
> So it wasn't broken. However there is some fuzziness
> in this area, for example the term "scsi_device".

Yes, but the block layer was not creating the proper symlink name, and
it would create multiple symlinks with the same name, in the same
directory, pointing to different places.  That had to be fixed, as it
was broken.  The block layer itself, has no way to determine if it is
using a scsi device, or another type of device, nor should it care.

thanks,

greg k-h

  reply	other threads:[~2006-02-22 18:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 17:59 lsscsi-0.17 released Douglas Gilbert
2006-02-22 18:37 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-21 23:39 Douglas Gilbert
2006-02-22  8:50 ` Matthias Andree
2006-02-22 15:01   ` Douglas Gilbert
2006-02-22 16:06     ` Matthias Andree
2006-02-22 16:27       ` Douglas Gilbert
2006-02-22 16:34         ` Matthew Wilcox
2006-02-22 16:38           ` Randy.Dunlap
2006-02-22 17:14           ` Greg KH
2006-02-22 18:00             ` Matthias Andree
2006-02-22 18:32               ` Greg KH
2006-02-22 20:22                 ` Matthias Andree

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=20060222183731.GB12542@kroah.com \
    --to=greg@kroah.com \
    --cc=dougg@torque.net \
    --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;
as well as URLs for NNTP newsgroup(s).