From: James Bottomley <James.Bottomley@SteelEye.com>
To: Heiko Carstens <Heiko.Carstens@de.ibm.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Greg Kroah-Hartman <greg@kroah.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] zfcp: kfree patch
Date: Mon, 10 Jan 2005 09:19:51 -0600 [thread overview]
Message-ID: <1105370391.4477.3.camel@mulgrave> (raw)
In-Reply-To: <OFF5A7977B.6DEBE53D-ONC1256F85.00246A36-C1256F85.0024C19A@de.ibm.com>
On Mon, 2005-01-10 at 07:41 +0100, Heiko Carstens wrote:
> What would keep the two release functions defined in
> scsi_transport_fc.c from being called _after_ the fc transport class
> module was unloaded? As usual I might be wrong but this looks like
> the same problem to me.
Object lifetime rules: devices which are attached to transport classes
must be serviced by HBAs which do the attachment. This makes the
transport class a required module for the HBA. So the transport class
can't be removed until all of the HBAs have been removed (which means
that all the objects they service have also been removed).
If you're asking how SCSI ensures that all the scsi_devices are
destroyed before the HBA driver is removed, we have a module reference
count system that means the HBA unload waits until everything
relinquishes the devices.
James
next prev parent reply other threads:[~2005-01-10 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 10:36 [PATCH] zfcp: kfree patch Heiko Carstens
2005-01-08 11:44 ` Arjan van de Ven
2005-01-10 6:41 ` Heiko Carstens
2005-01-10 15:19 ` James Bottomley [this message]
2005-01-08 22:33 ` Greg KH
2005-01-10 6:53 ` Heiko Carstens
2005-01-10 7:06 ` Greg KH
2005-01-10 8:10 ` Heiko Carstens
2005-01-10 8:18 ` Greg KH
2005-01-10 9:27 ` Heiko Carstens
2005-01-12 6:47 ` Greg KH
2005-01-12 8:48 ` Heiko Carstens
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=1105370391.4477.3.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Heiko.Carstens@de.ibm.com \
--cc=arjan@infradead.org \
--cc=greg@kroah.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