From: Krishna Murthy <krmurthy@cisco.com>
To: SCSI Mailing List <linux-scsi@vger.kernel.org>
Cc: davmyers@cisco.com
Subject: scsi_free_sdev and slave destroy
Date: Tue, 25 Nov 2003 20:37:34 +0530 [thread overview]
Message-ID: <200311252037.34015.krmurthy@cisco.com> (raw)
Hi,
I was going through the function
scsi_probe_and_add_lun().
It does
scsi_alloc_sdev
probe for the lun
If lun does not exist call scsi_free_sdev.
scsi_alloc_sdev calls slave_alloc of the HBA driver where as
scsi_free_sdev does not seem to call slave_destroy.
Please let me know if this is a bug or I am missing something.
Thanx
N.C.Krishna Murthy
next reply other threads:[~2003-11-25 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 15:07 Krishna Murthy [this message]
2003-11-25 15:23 ` scsi_free_sdev and slave destroy James Bottomley
2003-11-27 13:19 ` scsi_scan_target and SCSI_2 Krishna Murthy
2003-11-27 14:56 ` Peripheral qualifier 1 not considered in scsi_probe_and_add_lun Krishna Murthy
2003-11-27 15:55 ` James Bottomley
2003-11-27 15:37 ` scsi_scan_target and SCSI_2 James Bottomley
2003-11-27 15:45 ` Krishna Murthy
2003-11-27 15:57 ` James Bottomley
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=200311252037.34015.krmurthy@cisco.com \
--to=krmurthy@cisco.com \
--cc=davmyers@cisco.com \
--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).