From: Russell King <rmk@arm.linux.org.uk>
To: Frank v Waveren <fvw@var.cx>
Cc: Brian Gerst <bgerst@didntduck.org>,
Boris Dragovic <lynx@falcon.etf.bg.ac.yu>,
linux-kernel@vger.kernel.org
Subject: Re: negative mod use count
Date: Wed, 28 Feb 2001 23:01:53 +0000 [thread overview]
Message-ID: <20010228230153.A18738@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200102281958.UAA13226@falcon.etf.bg.ac.yu> <3A9D5AAB.E9AB4673@didntduck.org> <20010228213146.A1120@var.cx>
In-Reply-To: <20010228213146.A1120@var.cx>; from fvw@var.cx on Wed, Feb 28, 2001 at 09:31:46PM +0100
On Wed, Feb 28, 2001 at 09:31:46PM +0100, Frank v Waveren wrote:
> On Wed, Feb 28, 2001 at 03:08:11PM -0500, Brian Gerst wrote:
> > > what does negative module use count mean?
> > A bugged module.
>
> Not at all. A non-zero usage count means the module can't be unloaded.
> Whatever the module does with the usage count apart from that is
> completely it's own choice.
A negative module use count (specifically "-1") depends on whether a
module has a "can_unload" routine. If it does not have a "can_unload"
routine, then chances are either the module decided "I can never be
removed" or else the module is buggy.
However, if a "can_unload" routine does exist (as in ipv6) then the
module use count is unconditionally set to "-1".
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-02-28 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 19:58 negative mod use count Boris Dragovic
2001-02-28 20:08 ` Brian Gerst
2001-02-28 20:31 ` Frank v Waveren
2001-02-28 23:01 ` Russell King [this message]
2001-03-01 0:04 ` Keith Owens
2001-03-02 0:55 ` Dr. Kelsey Hudson
2001-03-02 10:17 ` Russell King
2001-03-02 13:30 ` Boris Dragovic
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=20010228230153.A18738@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=bgerst@didntduck.org \
--cc=fvw@var.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=lynx@falcon.etf.bg.ac.yu \
/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