Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 9 Sep 2002 18:52:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 9 Sep 2002 18:52:49 -0400 Received: from pc-62-30-255-50-az.blueyonder.co.uk ([62.30.255.50]:1959 "EHLO kushida.apsleyroad.org") by vger.kernel.org with ESMTP id ; Mon, 9 Sep 2002 18:52:48 -0400 Date: Mon, 9 Sep 2002 23:56:54 +0100 From: Jamie Lokier To: Daniel Phillips Cc: Alexander Viro , Rusty Russell , linux-kernel@vger.kernel.org Subject: Re: Question about pseudo filesystems Message-ID: <20020909235654.A5875@kushida.apsleyroad.org> References: <20020907192736.A22492@kushida.apsleyroad.org> <20020909204834.A5243@kushida.apsleyroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from phillips@arcor.de on Mon, Sep 09, 2002 at 10:12:28PM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1478 Lines: 30 Daniel Phillips wrote: > > The expected behaviour is as it has always been: rmmod fails if anyone > > is using the module, and succeeds if nobody is using the module. The > > garbage collection of modules is done using "rmmod -a" periodically, as > > it always has been. > > When you say 'rmmod modulename' the module is supposed to be removed, if > it can be. That is the user's expectation, and qualifies as 'obviously > correct'. > > Garbage collecting should *not* be the primary mechanism for removing > modules, that is what rmmod is for. Neither should a filesystem module > magically disappear from the system just because the last mount went > away, unless the module writer very specifically desires that. This is > where the obfuscating opinion is coming from: Al has come up with an > application where he wants the magic disappearing behavior and wants > to impose it on the rest of the world, regardless of whether it makes > sense. I think you've misunderstood. The module does _not_ disappear when the last file reference is closed. It's reference count is decremented, that is all. Just the same as if you managed the reference count yourself. You still need rmmod to actually remove the module. -- Jamie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/