public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Amrut Joshi <amrut.joshi@gmail.com>
To: linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: SCSI luns
Date: Tue, 12 Jul 2005 17:25:20 +0530	[thread overview]
Message-ID: <1ba727770507120455789aaf0a@mail.gmail.com> (raw)
In-Reply-To: <1121168331.3171.21.camel@laptopd505.fenrus.org>

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

Hi,

On 7/12/05, Arjan van de Ven <arjan@infradead.org> wrote:
> On Tue, 2005-07-12 at 16:52 +0530, Amrut Joshi wrote:
> > Hi,
> >
> > Currently linux scsi subsystem doesnt store the 8-byte luns which are
> > recieved in REPORT_LUNS reply. This information is forver lost once
> > the scan is over. In my LDD  I need this information. Currently I have
> > to snoop REPORT_LUNS reply, do scsilun_to_int for all the luns and
> 
> which LDD is this? Is it ready for merging into the linux kernel yet?
> 

It will be ready for submission in a couple of months. The design (and
implementation) would be simplified if these changes are accepted. Any
thoughts?

Sorry for the garbled patch. Attaching it again. 

Please CC me on the replies.

Thanks,
-Amrut!

[-- Attachment #2: patch --]
[-- Type: application/octet-stream, Size: 821 bytes --]

--- drivers/scsi/scsi_scan.c.orig	2005-06-30 04:30:53.000000000 +0530
+++ drivers/scsi/scsi_scan.c	2005-07-12 16:19:48.533788528 +0530
@@ -1170,6 +1170,7 @@
 				       " aborted\n", devname, lun);
 				break;
 			}
+                        memcpy(sdev->lun_address, lunp, sizeof(sdev->lun_address));
 		}
 	}
 
--- include/scsi/scsi_device.h.orig	2005-06-30 04:30:53.000000000 +0530
+++ include/scsi/scsi_device.h	2005-07-12 16:19:48.534788376 +0530
@@ -58,6 +58,8 @@
 					   could all be from the same event. */
 
 	unsigned int id, lun, channel;
+        struct scsi_lun lun_address;    /* scsi address returned by REPORT_LUNS
+                                         * usable only if sdev->scsi_lun >= SCSI_3 */
 
 	unsigned int manufacturer;	/* Manufacturer of device, for using 
 					 * vendor-specific cmd's */

  reply	other threads:[~2005-07-12 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1ba727770507120422562d525d@mail.gmail.com>
2005-07-12 11:38 ` SCSI luns Arjan van de Ven
2005-07-12 11:55   ` Amrut Joshi [this message]
2005-07-12 16:17   ` James Bottomley
2005-07-15 18:00     ` Patrick Mansfield

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=1ba727770507120455789aaf0a@mail.gmail.com \
    --to=amrut.joshi@gmail.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