From: Christoph Hellwig <hch@caldera.de>
To: root@chaos.analogic.com ("Richard B. Johnson")
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
Brian Gerst <bgerst@didntduck.org>
Subject: Re: Module open() problems, Linux 2.4.0
Date: Thu, 9 Nov 2000 21:22:28 +0100 [thread overview]
Message-ID: <200011092022.VAA03494@ns.caldera.de> (raw)
In-Reply-To: <Pine.LNX.3.95.1001109150621.15404A-100000@chaos.analogic.com>
In article <Pine.LNX.3.95.1001109150621.15404A-100000@chaos.analogic.com> you wrote:
> This may be, as you say, "harmless". It is, however, a bug. The
> reporting must be correct or large complex systems can't be
> developed or maintained.
No. It is not. The module usage count doesn't have a direct relation
to the number of open devices. The module count just makes the modules
un-removable if it is non-zero. It doesn't matter at all, when and where
you in- and decrease it, as long as the module is always protected against
unload when in use (e.g. opened).
Christoph
--
Always remember that you are unique. Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-09 20:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 19:00 Module open() problems, Linux 2.4.0 Richard B. Johnson
2000-11-09 19:27 ` Brian Gerst
2000-11-09 20:12 ` Richard B. Johnson
2000-11-09 20:22 ` Christoph Hellwig [this message]
2000-11-09 20:27 ` Jeff Garzik
2000-11-09 20:57 ` Richard B. Johnson
2000-11-09 21:02 ` Jeff Garzik
2000-11-09 21:05 ` Christoph Hellwig
2000-11-10 0:01 ` Olaf Titz
2000-11-09 20:27 ` Brian Gerst
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=200011092022.VAA03494@ns.caldera.de \
--to=hch@caldera.de \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.