From: Ben Collins <bcollins@debian.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
linux1394-devel@lists.sourceforge.net,
Ben Collins <bcollins@debian.org>
Subject: Re: sbp2: modprobe -r fails, module allegedly in use
Date: Sun, 10 Jul 2005 13:37:32 -0400 [thread overview]
Message-ID: <20050710173732.GF14956@phunnypharm.org> (raw)
In-Reply-To: <1121016562.5078.15.camel@mulgrave>
> Actually, I think your error is the opposite of this: you should never
> have to do a scsi_host_put() unless you did a corresponding
> scsi_host_get(), which, as far as I can see, sbp2 never does, so the
> extra put should be meaningless.
>
> Except, I notice that you don't do a scsi_device_put() after
> scsi_add_device(). I think this is probably the source of the
> refcounting errors: scsi_add_device returns an sdev with the refcount
> incremented by one, so you need to decrement the count after you've
> finished with it (in your case, you do nothing with it, so just
> decrement after you've checked it's not an error pointer).
Thanks. Stefan, can you test with that change? I've already put it in the
repo.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
SwissDisk - http://www.swissdisk.com/
next prev parent reply other threads:[~2005-07-10 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-10 14:42 sbp2: modprobe -r fails, module allegedly in use Stefan Richter
2005-07-10 15:07 ` Stefan Richter
2005-07-10 15:31 ` Ben Collins
2005-07-10 17:40 ` Christoph Hellwig
2005-07-10 17:46 ` Ben Collins
2005-07-10 17:49 ` Christoph Hellwig
2005-07-10 17:52 ` Ben Collins
2005-07-10 17:29 ` James Bottomley
2005-07-10 17:37 ` Ben Collins [this message]
2005-07-10 17:51 ` Stefan Richter
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=20050710173732.GF14956@phunnypharm.org \
--to=bcollins@debian.org \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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