From: Greg KH <greg@kroah.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <htejun@gmail.com>, Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org, Adrian Bunk <bunk@stusta.de>
Subject: Re: kref refcounting breakage in mainline
Date: Thu, 15 Mar 2007 07:54:14 -0700 [thread overview]
Message-ID: <20070315145414.GA18542@kroah.com> (raw)
In-Reply-To: <1173947546.6624.29.camel@Homer.simpson.net> <1173953960.6624.45.camel@Homer.simpson.net>
On Thu, Mar 15, 2007 at 11:19:20AM +0100, Mike Galbraith wrote:
> On Thu, 2007-03-15 at 01:06 -0700, Greg KH wrote:
>
> > That's good. But why don't we have a module name for this driver?
> >
> > And if we don't have a module name, why would there be a symlink to
> > remove? That's what is keeping your module from unloading, right?
>
> You keep saying "module", and that's making me a bit nervous ;-)
>
> Just to be sure we're not talking past each other, when you say module,
> don't mean the modprobe kind... i hope. This "module" as in driver is
> compiled in. (said that before, but you may have missed it)
Ahh, that changes everything here, thanks for letting me know, I had
missed this.
The problem is that the module_init() is failing, yet this isn't really
a module, it's built into the kernel. So some of the module teardown
logic is dieing when it thinks that we really have a full module
structure here (owner and such).
I'll look at this further tomorrow, as I'm travelling pretty much all
day today, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2007-03-15 15:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 8:58 kref refcounting breakage in mainline Andrew Morton
2007-03-03 5:48 ` Greg KH
2007-03-06 0:25 ` Greg KH
2007-03-06 5:43 ` Mike Galbraith
2007-03-06 21:04 ` Greg KH
2007-03-07 5:38 ` Mike Galbraith
2007-03-10 15:44 ` Mike Galbraith
2007-03-10 16:03 ` Mike Galbraith
2007-03-15 5:27 ` Greg KH
2007-03-15 7:53 ` Mike Galbraith
2007-03-15 8:06 ` Greg KH
2007-03-15 8:32 ` Mike Galbraith
2007-03-15 9:39 ` Mike Galbraith
[not found] ` <1173953960.6624.45.camel@Homer.simpson.net>
2007-03-15 14:54 ` Greg KH [this message]
2007-03-19 23:41 ` Randy Dunlap
2007-03-06 12:11 ` Mel Gorman
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=20070315145414.GA18542@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=efault@gmx.de \
--cc=htejun@gmail.com \
--cc=kay.sievers@vrfy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox