public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>, greg@kroah.com
Subject: Re: [PATCH] update sd to use kref and fix open/release race
Date: Tue, 13 Apr 2004 10:12:08 -0700	[thread overview]
Message-ID: <20040413171208.GA2550@us.ibm.com> (raw)
In-Reply-To: <1081518779.2203.29.camel@mulgrave>

James Bottomley [James.Bottomley@steeleye.com] wrote:
> @@ -1338,17 +1338,19 @@
>  	if ((sdp->type != TYPE_DISK) && (sdp->type != TYPE_MOD))
>  		goto out;
>  
> +	if ((error = scsi_device_get(sdp)) != 0)
> +		goto out;
> +
>  	SCSI_LOG_HLQUEUE(3, printk("sd_attach: scsi device: <%d,%d,%d,%d>\n", 
>  			 sdp->host->host_no, sdp->channel, sdp->id, sdp->lun));
>  
>  	error = -ENOMEM;
>  	sdkp = kmalloc(sizeof(*sdkp), GFP_KERNEL);

Did we decide through the thread on this issue that we will not allow a
rmmod to happen anymore unless you manually delete the children devices
off the host? In using scsi_debug I am not able to rmmod until I delete
all the children (i.e. sd's).

The parent child hierarchy should be held in place through kobject_add /
kobject_get of the parent so I would believe that the extra
scsi_device_get should not be needed.

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


  parent reply	other threads:[~2004-04-13 18:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-09 13:52 [PATCH] update sd to use kref and fix open/release race James Bottomley
2004-04-09 16:56 ` Patrick Mansfield
2004-04-09 17:17   ` Patrick Mansfield
2004-04-09 19:19     ` James Bottomley
2004-04-09 19:32       ` Greg KH
2004-04-09 19:57       ` Patrick Mansfield
2004-04-13 17:12 ` Mike Anderson [this message]
2004-04-21 19:10   ` James Bottomley
2004-04-22  5:57     ` Mike Anderson
2004-04-22  6:56       ` viro

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=20040413171208.GA2550@us.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Bottomley@steeleye.com \
    --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