[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20070319164123.756b43a7.randy.dunlap@oracle.com>
Date: Mon, 19 Mar 2007 16:41:23 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Greg KH <greg@...ah.com>
Cc: Mike Galbraith <efault@....de>,
Andrew Morton <akpm@...ux-foundation.org>,
Tejun Heo <htejun@...il.com>,
Kay Sievers <kay.sievers@...y.org>,
linux-kernel@...r.kernel.org, Adrian Bunk <bunk@...sta.de>
Subject: Re: kref refcounting breakage in mainline
On Thu, 15 Mar 2007 07:54:14 -0700 Greg KH wrote:
> 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).
Urgh, it's not a "loadable" module, but it's still a logical module.
> I'll look at this further tomorrow, as I'm travelling pretty much all
> day today, sorry.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists