From: Amrut Joshi <amrut.joshi@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: SCSI luns
Date: Tue, 12 Jul 2005 16:52:54 +0530 [thread overview]
Message-ID: <1ba727770507120422562d525d@mail.gmail.com> (raw)
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
store this mapping somewhere. This can be simplified by storing it in
scsi_device. This field will be meaningful only if sdev->scsi_level >=
SCSI_3.
Heres the patch
-----------------------------------------------------------------------------------------------------------------
--- 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 */
----------------------------------------------------------------------------------------------------------------------
Please CC replies to me as I am not on the list.
Thanks,
-Amrut!
next reply other threads:[~2005-07-12 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 11:22 Amrut Joshi [this message]
2005-07-12 11:38 ` SCSI luns Arjan van de Ven
2005-07-12 11:55 ` Amrut Joshi
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=1ba727770507120422562d525d@mail.gmail.com \
--to=amrut.joshi@gmail.com \
--cc=linux-kernel@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