public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: [RFC] scsi host sysfs support again [0/4]
Date: Mon, 5 May 2003 03:00:56 -0700	[thread overview]
Message-ID: <20030505100056.GI8416@beaverton.ibm.com> (raw)
In-Reply-To: <3EB63188.3080703@torque.net>

Douglas Gilbert [dougg@torque.net] wrote:
> [HBA REMOVAL new]
> LLD                      mid level                 LLD
> ---                      ---------                 ---
> scsi_remove_host() ---------+
>                             |
>                      slave_destroy()
>                      slave_destroy()
>                         release()     -->     scsi_unregister()
> 
> In the new model there is nothing left to do after
> scsi_remove_host() has finished since everything happened
> during that call. The the LLD is re-entered to cleanup
> up any HBA specific device resources (slave_destroy()).
> Finally the LLD is re-entered by the release().
> 
> Also module unloads (should) use the ->remove
> method as well. Does the LLD need to know
> whether a HBA removal is hot or not?
> 

I believe Christoph is indicating that if something has a ref on
scsi_host and this causes the release to be called after the return from
scsi_remove_host than this would not be good. I believe the LLDD model
would stay like the old method except in the mid layer there would be a
change in how / when kfree(shost) is called.

LLD			mid level
scsi_remove_host()  -----+
                         |
		     slave_destroy()
		     slave_destroy()
		     slave_destroy()
scsi_unregister()  ------+
			 |
			 kfree of scsi_host may happen here or sometime
			 later depending on the ref count.


-andmike
--
Michael Anderson
andmike@us.ibm.com


  reply	other threads:[~2003-05-05  9:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05  8:33 [RFC] scsi host sysfs support again [0/4] Mike Anderson
2003-05-05  8:34 ` [RFC] scsi host sysfs support again [1/4] Mike Anderson
2003-05-05  8:35   ` [RFC] scsi host sysfs support again [2/4] Mike Anderson
2003-05-05  8:37     ` [RFC] scsi host sysfs support again [3/4] Mike Anderson
2003-05-05  8:38       ` [RFC] scsi host sysfs support again [4/4] Mike Anderson
2003-05-05  8:38 ` [RFC] scsi host sysfs support again [0/4] Christoph Hellwig
2003-05-05  9:40   ` Douglas Gilbert
2003-05-05 10:00     ` Mike Anderson [this message]
2003-05-05  9:48   ` Mike Anderson
2003-05-05 10:17     ` Christoph Hellwig
2003-05-06  1:05       ` Mike Anderson
2003-05-07 15:44         ` Christoph Hellwig
2003-05-07 16:15           ` Mike Anderson
2003-05-07 16:41             ` Christoph Hellwig
2003-05-05 11:46 ` Douglas Gilbert
2003-05-05 21:45   ` Mike Anderson
2003-05-06  1:12     ` Douglas Gilbert
2003-05-06 16:28 ` James Bottomley
2003-05-06 17:23   ` Mike Anderson
2003-05-07 23:19     ` Willem Riede
2003-05-08  0:09       ` Douglas Gilbert
2003-05-08  1:44       ` Mike Anderson

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=20030505100056.GI8416@beaverton.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=dougg@torque.net \
    --cc=hch@infradead.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