From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: root@chaos.analogic.com
Cc: Brian Gerst <bgerst@didntduck.org>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Module open() problems, Linux 2.4.0
Date: Thu, 09 Nov 2000 16:02:43 -0500 [thread overview]
Message-ID: <3A0B10F3.32A14DF4@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1001109154744.16836A-100000@chaos.analogic.com>
"Richard B. Johnson" wrote:
> I suppose. Look at what you just stated! This means that a reported
> value is now worthless.
>
> To restate, somebody decided that we didn't need this reported value
> anymore. Therefore, it is okay to make it worthless.
>
> I don't agree. The De-facto standard has been that the module usage
> count is equal to the open count. This became the standard because
> of a long established history.
>
> This is one of the tools we use to verify that an entire system
> is functioning properly. Now, somebody decided that I didn't need
> this tool.
You assumed the module count == device open count, when that was in fact
never the case. The 2.4.x kernel changes merely shattered false
assumptions you held on your part.
The kernel thread example I described in my last e-mail holds true for
kernel 2.2.x as well, maybe 2.0.x too.
Jeff
--
Jeff Garzik |
Building 1024 | Would you like a Twinkie?
MandrakeSoft |
-
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 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 19:00 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
2000-11-09 20:27 ` Jeff Garzik
2000-11-09 20:57 ` Richard B. Johnson
2000-11-09 21:02 ` Jeff Garzik [this message]
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=3A0B10F3.32A14DF4@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®