From: Pete Wyckoff <pw@osc.edu>
To: David Dillow <dave@thedillows.org>
Cc: linux-kernel@vger.kernel.org, general@lists.openfabrics.org
Subject: Re: [ofa-general] Re: list corruption on ib_srp load in v2.6.24-rc5
Date: Sat, 22 Dec 2007 10:15:59 -0500 [thread overview]
Message-ID: <20071222151559.GB10085@osc.edu> (raw)
In-Reply-To: <1198275532.9979.43.camel@lap75545.ornl.gov>
dave@thedillows.org wrote on Fri, 21 Dec 2007 17:18 -0500:
> On Fri, 2007-12-21 at 16:52 -0500, David Dillow wrote:
> > I'm getting the following oops when doing the following commands:
> >
> > modprobe ib_srp
> > <add targets(s) to ib_srp using sysfs>
> > rmmod ib_srp
> > modprobe ib_srp
> > <OOPS>
> >
> > I'm going to try and track down how the list is getting corrupted; it
> > looks like attribute_container_list in
> > drivers/base/attribute_container.c is the one getting corrupted.
>
> Ok, found the culprit, now to figure out the motive and fix it.
>
> ib_srp's srp_cleanup_module calls srp_release_transport(), which calls
> transport_container_unregister() for the rport_attr_cont member of
> struct srp_internal.
>
> That last unregister call is returning -EBUSY, but it gets ignored, and
> the list node gets erased (or just reused) when the module's text/memory
> is free'd.
>
> Now, to see if ib_srp should be waiting for everything to be destroyed
> before calling srp_release_transport(), or if it is just not removing
> some attributes properly.
I don't see where srp_cleanup_module() is calling srp_remove_host().
That is the likely way that transport devices should be made to go
away. Something on the order of srp_remove_work().
Or srp_remove_one() except with a call to srp_remove_host() may be
necessary. In fact, maybe just adding that call will fix it, as
ib_unregister_client should drive the remove function. Guesses, all
this.
-- Pete
next prev parent reply other threads:[~2007-12-22 15:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 21:52 list corruption on ib_srp load in v2.6.24-rc5 David Dillow
2007-12-21 21:54 ` David Dillow
2007-12-21 22:18 ` David Dillow
2007-12-22 15:15 ` Pete Wyckoff [this message]
2007-12-22 16:41 ` FUJITA Tomonori
2007-12-22 17:32 ` Dave Dillow
2007-12-26 17:14 ` David Dillow
2007-12-27 2:58 ` FUJITA Tomonori
2007-12-27 17:53 ` David Dillow
2008-01-02 17:51 ` Roland Dreier
2008-01-03 8:30 ` FUJITA Tomonori
2008-01-03 20:09 ` [ofa-general] " David Dillow
2008-01-03 20:51 ` David Dillow
2008-01-03 21:33 ` Roland Dreier
2008-01-04 0:47 ` FUJITA Tomonori
2008-01-04 2:34 ` [ofa-general] [2.6.24-rc BUGFIX] SRP transport: only remove our own entries Dave Dillow
2008-01-04 2:34 ` Dave Dillow
2008-01-04 2:54 ` [ofa-general] " FUJITA Tomonori
2008-01-04 2:54 ` FUJITA Tomonori
2008-01-04 2:39 ` [2.6.24-rc BUGFIX] IB/srp: release transport when removing host Dave Dillow
2008-01-04 2:54 ` FUJITA Tomonori
2008-01-04 3:35 ` [2.6.24-rc minor bugfix] IB/srp: release transport before " Dave Dillow
2008-01-08 20:09 ` Roland Dreier
2007-12-21 22:21 ` [ofa-general] list corruption on ib_srp load in v2.6.24-rc5 Roland Dreier
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=20071222151559.GB10085@osc.edu \
--to=pw@osc.edu \
--cc=dave@thedillows.org \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@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 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.