From: scameron@beardog.cce.hp.com
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Jens Axboe <jens.axboe@oracle.com>,
Douglas Gilbert <dgilbert@interlog.com>,
linux-scsi@vger.kernel.org,
James.Bottomley@HansenPartnership.com, mikem@beardog.cce.hp.com,
dab@hp.com, hch@infradead.org,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Subject: Re: Is this a known problem with the SCSI mid layer?
Date: Fri, 15 Jan 2010 15:44:55 -0600 [thread overview]
Message-ID: <20100115214455.GG13413@beardog.cce.hp.com> (raw)
In-Reply-To: <tkrat.956a5012a91df155@s5r6.in-berlin.de>
On Fri, Jan 15, 2010 at 10:03:09AM +0100, Stefan Richter wrote:
> On 15 Jan, Jens Axboe wrote:
> > On Fri, Jan 15 2010, Stefan Richter wrote:
> >> The sg driver's open method takes a reference to the underlying SCSI
> >> device representation of the mid layer. Among else, this step increases
> >> the module use count of the respective low-level driver
> ...
> >> In short, it is normal, expected, and necessary what you are seeing.
> >
> > Hmm... Unless I'm reading Stephens email incorrectly, he's holding the
> > device open, removing it, closing the device, and then attempting to
> > remove the host driver. So at the point that he wants to rmmod the
> > module, there is indeed no references to it anymore.
> >
> > It looks like a bug.
>
> Oh, right, I missed that the device file was indeed closed ( = the
> seemingly last user of it exited) before rmmod was attempted.
>
> I.e. remove-single-device while an sg file is open leaves a dangling
> reference, while remove-single-device while an sd file is open does
> not...
> --
> Stefan Richter
> -=====-==-=- ---= -====
> http://arcgraph.de/sr/
>
I've since tried this on a newer kernel, 2.6.33rc4 (previously I
was using a 2.6.27 kernel).
With the 2.6.33rc4 kernel, so far the problem hasn't appeared.
Thanks, and sorry I didn't try the newer kernel first.
-- steve
next prev parent reply other threads:[~2010-01-15 21:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 16:56 Is this a known problem with the SCSI mid layer? scameron
2010-01-14 18:24 ` Douglas Gilbert
2010-01-14 19:00 ` scameron
2010-01-14 20:07 ` scameron
2010-01-14 23:43 ` Stefan Richter
2010-01-15 8:10 ` Jens Axboe
2010-01-15 9:03 ` Stefan Richter
2010-01-15 21:44 ` scameron [this message]
2010-01-16 11:47 ` FUJITA Tomonori
-- strict thread matches above, loose matches on Subject: below --
2010-01-15 2:14 Stephen Cameron
2010-01-15 13:02 ` Stefan Richter
2010-01-15 14:18 ` Stephen Cameron
2010-01-15 17:50 ` Douglas Gilbert
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=20100115214455.GG13413@beardog.cce.hp.com \
--to=scameron@beardog.cce.hp.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dab@hp.com \
--cc=dgilbert@interlog.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hch@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mikem@beardog.cce.hp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.