[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070424094648.43d2b9b4@gondolin.boeblingen.de.ibm.com>
Date: Tue, 24 Apr 2007 09:46:48 +0200
From: Cornelia Huck <cornelia.huck@...ibm.com>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Linas Vepstas <linas@...tin.ibm.com>,
Christoph Hellwig <hch@...radead.org>,
"<Andrew Morton" <akpm@...l.org>, containers@...ts.osdl.org,
Oleg Nesterov <oleg@...sign.ru>, linux-kernel@...r.kernel.org,
Paul Mackerras <paulus@...ba.org>, linux-s390@...r.kernel.org,
linuxppc-dev@...abs.org
Subject: Re: [PATCH] powerpc pseries eeh: Convert to kthread API
On Tue, 24 Apr 2007 15:00:42 +1000,
Benjamin Herrenschmidt <benh@...nel.crashing.org> wrote:
> Like anything else, modules should have separated the entrypoints for
>
> - Initiating a removal request
> - Releasing the module
>
> The former is use did "rmmod", can unregister things from subsystems,
> etc... (and can file if the driver decides to refuse removal requests
> when it's busy doing things or whatever policy that module wants to
> implement).
>
> The later is called when all references to the modules have been
> dropped, it's a bit like the kref "release" (and could be implemented as
> one).
That sounds quite similar to the problems we have with kobject
refcounting vs. module unloading. The patchset I posted at
http://marc.info/?l=linux-kernel&m=117679014404994&w=2 exposes the
refcount of the kobject embedded in the module. Maybe the kthread code
could use that reference as well?
-
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