From: Nathan Lynch <ntl@pobox.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sysfs-related oops during module unload (2.6.16-rc2)
Date: Sat, 18 Feb 2006 18:47:51 -0600 [thread overview]
Message-ID: <20060219004751.GE3293@localhost.localdomain> (raw)
In-Reply-To: <20060216215023.GA30417@kroah.com>
Greg KH wrote:
> On Sat, Feb 11, 2006 at 09:38:49PM -0800, Greg KH wrote:
> > On Sat, Feb 11, 2006 at 11:27:52PM -0600, Nathan Lynch wrote:
> > > Greg KH wrote:
> > > > On Sat, Feb 11, 2006 at 04:03:53PM -0600, Nathan Lynch wrote:
> > > > > If the refcnt attribute of a module is open when the module is
> > > > > unloaded, we get an oops when the file is closed. I used ide_cd for
> > > > > this report but I don't think the oops is caused by the driver itself.
> > > > > This bug seems to be restricted to the /sys/module hierarchy; it
> > > > > doesn't happen with /sys/class etc.
<snip>
>
> Ok, turns out the code was trying to increment the module reference
> count correctly, but it wasn't working right at all. And we were not
> showing a few things in sysfs if module unload was not selected, which
> isn't right.
>
> So here's a patch that fixes all of this, and your original problem.
> Bonus is that it actually removes more code than it adds :)
>
> Can you test it out to verify that it works for you?
Sorry for the delay.
Tested against 2.6.16-rc4-ish, and it seems to do the right thing --
modprobe -r says the module is busy while the refcnt attribute is
open. The module is allowed to unload once the file is closed.
I didn't verify the other stuff your patch changes, though.
Thanks.
Nathan
next prev parent reply other threads:[~2006-02-19 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 22:03 sysfs-related oops during module unload (2.6.16-rc2) Nathan Lynch
2006-02-11 22:45 ` Greg KH
2006-02-12 5:27 ` Nathan Lynch
2006-02-12 5:38 ` Greg KH
2006-02-16 21:50 ` Greg KH
[not found] ` <200602162253.45621.dtor_core@ameritech.net>
2006-02-18 0:36 ` Greg KH
2006-02-19 0:47 ` Nathan Lynch [this message]
2006-02-19 0:57 ` Greg KH
2006-02-21 5:50 ` Nathan Lynch
2006-02-21 6:12 ` Greg KH
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=20060219004751.GE3293@localhost.localdomain \
--to=ntl@pobox.com \
--cc=greg@kroah.com \
--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.