From: FUJITA Tomonori <tomof@acm.org>
To: dave@thedillows.org
Cc: linux-kernel@vger.kernel.org, general@lists.openfabrics.org, pw@osc.edu
Cc: fujita.tomonori@lab.ntt.co.jp
Subject: Re: list corruption on ib_srp load in v2.6.24-rc5
Date: Sun, 23 Dec 2007 01:41:03 +0900 [thread overview]
Message-ID: <20071223014407L.tomof@acm.org> (raw)
In-Reply-To: <1198275532.9979.43.camel@lap75545.ornl.gov>
On Fri, 21 Dec 2007 17:18:52 -0500
David Dillow <dave@thedillows.org> wrote:
>
> 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.
transport_container_unregister(&i->rport_attr_cont) should not fail here.
It fails because there is still a srp rport.
I think that as Pete pointed out, srp_remove_one needs to call
srp_remove_host.
Can you try this?
Thanks,
diff --git a/drivers/infiniband/ulp/srp/ib_srp.c b/drivers/infiniband/ulp/srp/ib_srp.c
index 950228f..bdb6f85 100644
--- a/drivers/infiniband/ulp/srp/ib_srp.c
+++ b/drivers/infiniband/ulp/srp/ib_srp.c
@@ -2053,6 +2053,7 @@ static void srp_remove_one(struct ib_device *device)
list_for_each_entry_safe(target, tmp_target,
&host->target_list, list) {
+ srp_remove_host(target->scsi_host);
scsi_remove_host(target->scsi_host);
srp_disconnect_target(target);
ib_destroy_cm_id(target->cm_id);
next prev parent reply other threads:[~2007-12-22 16:41 UTC|newest]
Thread overview: 22+ 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 ` [ofa-general] " Pete Wyckoff
2007-12-22 16:41 ` FUJITA Tomonori [this message]
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 ` [2.6.24-rc BUGFIX] SRP transport: only remove our own entries Dave Dillow
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=20071223014407L.tomof@acm.org \
--to=tomof@acm.org \
--cc=dave@thedillows.org \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pw@osc.edu \
/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;
as well as URLs for NNTP newsgroup(s).