[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1190677332.27805.229.camel@localhost.localdomain>
Date: Tue, 25 Sep 2007 09:42:12 +1000
From: Rusty Russell <rusty@...tcorp.com.au>
To: Tejun Heo <htejun@...il.com>
Cc: Jonathan Corbet <corbet@....net>, ebiederm@...ssion.com,
cornelia.huck@...ibm.com, greg@...ah.com,
stern@...land.harvard.edu, kay.sievers@...y.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] module: implement module_inhibit_unload()
On Tue, 2007-09-25 at 08:18 +0900, Tejun Heo wrote:
> > Given your description of this tool as a "sledgehammer," might it not be
> > easier to just take and hold module_mutex for the duration of the unload
> > block?
>
> That would be easier but...
>
> * It would serialize users of the sledgehammer.
> * It would block loading modules (which is often more important than
> unloading them) when things go south.
My concern is that you're dropping the module mutex around ->exit now.
I don't *think* this should matter, but it's worth considering.
I really wonder if an explicit "kill_this_attribute()" is a better way
to go than this...
Rusty.
-
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