From: Hugang <hugang@soulinfo.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, bcollins@debian.org
Subject: Re: [PATCH] fix rmmod sbp2 hang in 2.6.7
Date: Wed, 14 Jul 2004 17:29:57 +0800 [thread overview]
Message-ID: <20040714172957.52de0f9b@localhost> (raw)
In-Reply-To: <20040714102417.A12942@flint.arm.linux.org.uk>
On Wed, 14 Jul 2004 10:24:17 +0100
Russell King <rmk+lkml@arm.linux.org.uk> wrote:
| This down+up prevents drivers from being unloaded until there are no
| references to their struct device_driver. By removing this, you open
| the very real possibility for an oops to occur.
Yes, I agree with you. When sbp2 is using the module count is not zero,
so I can rmmod it, So I think, for sbp2 that's safe, That's true on my laptop.
|
| If you're waiting inside that function for the last reference to be
| dropped, the real question is why you still have references to it.
There are tree places that reference ->unload_sem in linux kernel tree, but I
don't known, why the same code in 2.6.4 can works fine. :)
bus.c:68: up(&drv->unload_sem);
driver.c:110: down(&drv->unload_sem);
driver.c:111: up(&drv->unload_sem);
--
Hu Gang / Steve
Linux Registered User 204016
GPG Public Key: http://soulinfo.com/~hugang/hugang.asc
next prev parent reply other threads:[~2004-07-14 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 3:48 [PATCH] fix rmmod sbp2 hang in 2.6.7 Hugang
2004-07-14 8:13 ` Hugang
2004-07-14 9:11 ` Hugang
2004-07-14 9:24 ` Russell King
2004-07-14 9:29 ` Hugang [this message]
2004-07-14 10:20 ` Russell King
2004-07-14 11:33 ` Ben Collins
2004-07-17 18:43 ` Tim Wright
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=20040714172957.52de0f9b@localhost \
--to=hugang@soulinfo.com \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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