From: jbradford@dial.pipex.com
To: wowbagger@sktc.net (David D. Hagood)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Driverfs updates
Date: Tue, 9 Jul 2002 15:43:30 +0100 (BST) [thread overview]
Message-ID: <200207091443.PAA02132@darkstar.example.net> (raw)
In-Reply-To: <3D2AD518.6090706@sktc.net> from "David D. Hagood" at Jul 09, 2002 07:20:40 AM
> It seems to me the problem is in designing modules to unload, and saying
> "Then don't unload them" is not even a band-aid - it is willful
> ignorance. If there is a potential race condition unloading a module,
> then the module is BROKEN.
Agreed. Unloading is as fundamental as loading - especially as a lot of users load and unload modules as a, (bad), way to use two incompatible devices on one port. Once you introude a bloatule (I.E. module that can't be unloaded), that stops working. As more and more people start relying on the behavior, it gets to be more of a problem.
John.
next prev parent reply other threads:[~2002-07-09 14:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 18:41 Driverfs updates Patrick Mochel
2002-07-08 23:33 ` Keith Owens
2002-07-08 23:52 ` Thunder from the hill
2002-07-09 0:09 ` Keith Owens
2002-07-09 8:30 ` Oliver Neukum
2002-07-09 11:08 ` Thunder from the hill
2002-07-09 11:45 ` Richard B. Johnson
2002-07-09 12:20 ` David D. Hagood
2002-07-09 12:33 ` Thunder from the hill
2002-07-09 14:43 ` jbradford [this message]
2002-07-10 7:15 ` jw schultz
2002-07-09 17:05 ` Oliver Neukum
2002-07-10 0:43 ` Pavel Machek
2002-07-09 16:56 ` Patrick Mochel
2002-07-09 23:29 ` Keith Owens
2002-07-10 20:02 ` Patrick Mochel
2002-07-11 0:40 ` John Alvord
-- strict thread matches above, loose matches on Subject: below --
2002-07-18 18:11 driverfs updates Patrick Mochel
2002-07-18 18:33 ` Greg KH
2002-07-18 19:57 ` Patrick Mochel
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=200207091443.PAA02132@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wowbagger@sktc.net \
/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